News for hackers. Stuff that matters.
Re:How ACH works: A developer perspective (2014) by dcow on Thursday August 24, 2017 @10:49PM (#15095765)
I don't know why everyone thinks they need an API to reimplement (poorly) basic unix functionality that's been around be for years.
Re:How ACH works: A developer perspective (2014) by Spivak on Friday August 25, 2017 @12:29AM (#15096124)
Especially when FTP and HTTP performance is basically comparable and will depend more on the network and storage than the protocol.

Have we gotten to the point where anything not HTTP is considered old?

Re:How ACH works: A developer perspective (2014) by digi_owl on Friday August 25, 2017 @05:34AM (#15097204)
never mind that most "API" are JSON (or some such) delivered over (S)HTTP anyways.

But yes, anything but HTTP is "old". In large part because of corporate firewall rules that block anything but HTTP traffic (and more often than not filter even that traffic).

Re:How ACH works: A developer perspective (2014) by joshribakoff on Friday August 25, 2017 @12:56AM (#15096213)
No. I'm referring to an API to query data in realtime instead of batching the entire freaking database and then having out dated snapshot of the data
Re:How ACH works: A developer perspective (2014) by EpicEng on Friday August 25, 2017 @01:05AM (#15096246)
>Because it didn't work in FileZilla, they didn't want to use it

Sounds like they didn't need much if any of what you did. They wanted X and you gave them Y. Y would require them to change the way they worked. Did they need query capability? Seems like they didn't and SFTP would have suited them better.

Honestly sounds to me like you went for an overly complex solution where something simple would have done just fine.

Re:How ACH works: A developer perspective (2014) by joshribakoff on Friday August 25, 2017 @02:00AM (#15096444)
Our company and their company have a common customer. Neither of us need each other we want to make our customer happy. Customer would be happiest with realtime data but company B wants to send snapshots via sftp. So I setup an endpoint that speaks sftp. They even told me to "do something" to make it secure. Then they complained I used a port other than 22 and that it only worked on the command line. It sounds like the problem is the other company doesn't want to do any work / wants to send the file manually. I don't see how I went for an overly complex solution. I attempted to do exactly what they asked and they moved the target so of course I missed. In fact it's this company that is just trying to avoid doing any programming. But that comes with the territory. I respect your opinion but disagree with you
Re:How ACH works: A developer perspective (2014) by EpicEng on Friday August 25, 2017 @09:27AM (#15098223)
Fair enough, I didn't have the backstory.
Re:How ACH works: A developer perspective (2014) by gaius on Friday August 25, 2017 @01:37AM (#15096353)
But but rewrite all the things in node.js!! Don't worry about understanding the file format, which is well established, or what the users of the file are actually doing with it, also well established, the important thing is node.js!!!

Frankly once they hear it's node.js the users should be bowing down to worship!!!!

Re:How ACH works: A developer perspective (2014) by joshribakoff on Friday August 25, 2017 @02:20AM (#15096527)
Actually I wanted him to make an https API for us to query real time data. I would have used PHP to consume his API because it's easier to find developers on our end and synchronous code is easier to maintain when performance is not a concern