It has been a while since I wrote the last post … I know, I’ve still quite a lot of stuff left opened but source sooner or later you’ll get it. Don’t worry 😉
get Actually they’re using a mix of http://www.apisalud.es/?supporting-statement-for-university supporting statement for university AMF and HTTP based API but, as long as the AMF implementation is unfortunately a bit unstable, they want to move to a full HTTP based API … that sounded quite easy: take a bit of HTTP, dress it with POST and maybe XML (or whatever other ingredient you like most) and you’ll have a good base to start porting the API.
go to site But I’ve ignored a small particular that turned out to be really painful to manage by using just HTTP: sending efficently to the server big chunks of binary data.
go to site Those were the requirements I had to fulfill:
- I have potentially really big binary files to be sent quickly to the server;
- I have to track upload progress somehow;
- I must be able to trigger the upload without the user interaction;
- I should rely on HTTP only;
http://pacificcrossroads.net/?essay-grammar-help And here the solutions I’ve tried to implement, and the conclusions I’ve achieved (well, I didn’t try all the options because I already knew that a few of them were not suitable for my situation, but they might be useful to someone and so I’m reporting them anyway).