You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Timothy Larson <Td...@ci.canton.oh.us> on 2002/12/09 17:48:50 UTC

Suggestions for flow

Suggestions for flowscript:

call(uri) -- use uri to generate data for internal use in flowscript
send(uri) -- create continuation and use uri to send data to the client
recv(uri) -- receive input from client, and if uri is not null, use it to process input
last(uri) -- use uri to send the last data to the client without creating a continuation

"call" allows the use of resources from the sitemap without causing
interaction with the client.

"send" and "recv" are split for improved responsiveness.
An update can be sent to the client and processing can continue, allowing us to
be almost ready to send the next update when the client response finally comes.

"send" and "last" are split for better resource allocation.
There is no need to creates a continuation it we are not going to continue.

Documentation should mention that code after a call to "last" involves trade-off.
The last page can be sent without without delay, but the client cannot be sure
that the processing gets completed successfully.  Sometimes this is OK.
For example, the processing of statistics about a user could be triggered when
the user logs out.  If the client does not need to know about the statistics,
the final page could be sent first, and the processing could be done second.
An administrator could see any errors in the logs or a custom status page.

Tim



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org