Yes the data will be small, so output buffering is ok. But I must to enable it on every URL that I want to handle this way.

I wonder if i could use global:set_lock(ID) whit ID = {Resource, Requester} and Requester is not the pid of the current process (the same as yaws worker) but something else, something unique to the Arg record, so it does not change on subsequent calls to the streaming process, but different on every request sot the locking mechanism doesn't change.

Appmod opaque data is static, Do you know if I can set it dynamically, tu put a ref() on it and use this ref as requester identifier ?


- lud

Le 04/06/2014 12:21, Christopher Faulet a écrit :
On 04/06/2014 11:33, Ludovic Demblans wrote:
Is there a way to force the data to be sent in one block ? I do not need 
streaming (at least for these URLs/resources), I just want to 
communicate via the client with small bits of data (mostly JSON).

In Yaws, you cannot. Nevertheless, you can "bufferize" your response in
PHP. See All will be
done before php sends the response data, so it does not matter if Yaws
streams them or not (of course the response must be reasonably small).

Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!

Erlyaws-list mailing list