A long journey through chunked transfer and file uploading

It has been a while since I wrote the last post … I know, I’ve still quite a lot of stuff left opened but http://www.fcoss.nl/?essay-wuthering-heights Essay Wuthering Heights sooner or later you’ll get it. Buy An Essay For 5 Don’t worry 😉

Graduate Writing Services During the last days I’ve been working on improving some server side API for a client I’m working for.

Science Paper Writing Service Actually they’re using a mix of 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.

Essay Online Proofreader

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.

Essay Writing Service Vancouver Bc

Discount Genuine Viagra Those were the requirements I had to fulfill:

  1. I have potentially really big binary files to be sent quickly to the server;
  2. I have to track upload progress somehow;
  3. I must be able to trigger the upload without the user interaction;
  4. I should rely on HTTP only;

An Argument Essay About Global Warming 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).

Continue reading

http://www.kaufhaushessen.de/cms/?writing-company Writing Company