Re: [Cppcms-users] upload progress

[Artyom <art...@ya...>]

> hi,
> 
> 
> i  implemented some global object to track running uploads in cppcms.
> after i  got it running i learned that nginx buffers the _complete_ post
> before  sending it to the fastcgi backend. this is by design and  not
> alterable.

Ok, its quite sad, -1 more point for Nginx for me.

> - cppcms with nginx can  not be used to 'stream' post data directly to
>   cppcms backend in fastcgi  mode
> - nginx always cashes post requests and sends them then completely  to
> the fastcgi backend (cppcms) which does not block cppcms while  receiving
> data from a slow connection (which could be a good thing)

Ok, it is good point to remember this in future, probably even
it is good to add it to the wiki at some point

> though this is not really new it might help a  little bit. it's fo sure
> something to be mentioned in the documentation when  the upload handling
> is changed in RC1.

It would not be "changed" but rather enhanced so users would be able
to have better control over uploads that today if they want.

In any case as preparation to future implementation of web-sockets
API I think I'll add an asynchronous API for fetching POST data.

But this is in TODO list.

> as i understood this will offer the  possibility to
> abort a running upload; well if you have nginx in front it  might not
> work as  expected.

This is mostly web server issue, to be honest, almost every web server has 
its own quirks, for example only nginx reports on closed-by-peer connections
lighttpd and apache don't do this at all.


Regards,
  Artyom