Saraswati and GWT

[asif...@gmail.com]

Hi,

I am looking to develop a web application with Sarasvati as the workflow/statemachine - and GWT as the front end

Some conceptual roadblock that I am facing is

1>. Sarasvati has to obviously run in the server side - with client side GWT triggering the workflow and getting the nodes for action
But this would involve multiple server round trips using GWT-RPC, requestbuilder - does this incur considerable delays in the front-end?
Has anybody a similar use-case?

Or is the latency negligible?

thanks and regards,

[Paul Lorenz]

The latency incurred in processing a workflow step depends on your persistence model and your node logic. If you are running in memory and your node doesn't do much heavy lifting, then the latency should be really tiny. Using the hibernate backend will add some latency, though it should not be huge, unless you have a slow or overloaded DB or massive graphs. The latency in your custom nodes is up to you.

--
You received this message because you are subscribed to the Google Groups "sarasvati-wf-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sarasvati-wf-us...@googlegroups.com.
To post to this group, send email to sarasvati...@googlegroups.com.
Visit this group at http://groups.google.com/group/sarasvati-wf-users.
For more options, visit https://groups.google.com/groups/opt_out.