Re: RequestFactory queue manager (network retry etc)... already exist and/or worth making FOSS?

Hi Thomas,

I really do struggle with RequestBatcher sorry... However is it correct that it uses a single RequestContext? and that if any Request in a RequestContext is a success or a failure then the whole RequestContext is locked? That is the basis I was working on. Be very glad (if feel a bit foolish) if that is not the case.

NonAtomicBatch sends things over the same HTTP request but with multiple RequestContexts.

I'll try and get the OK from my boss to get this onto github.

Cheers

Sam

On Friday, July 12, 2013 10:29:05 AM UTC+1, Thomas Broyer wrote:

On Friday, July 12, 2013 10:42:05 AM UTC+2, salk31 wrote:

Hi Jens,

Thomas has tried to explain RequestBatcher to me but my understanding is that this essentially merges multiple RequestContexts.

RequestBatcher is about automatically firing the RequestContext in a scheduleFinally; merging RequestContexts is distinct, it's the append() method from RequestContext, which can be used independently of RequestBatcher.

 

One of our uses cases is to send the current contents of a form to the server then have the server generate a report on the latest state of that form. The user then goes on to just save that form as usual.

If we used RequestBatcher wouldn't that mean the extra RequestContexts are attached for good?

We have fiddled with the RequestTransport. I think our requirements are pretty generic though so worth having a community effort for an off the shelf solution?

If you think it's worth open-sourcing, then I'd say just do it and see what feedback you get.

For my own needs, I only needed to handle authentication failure, and this is rather easy: https://github.com/tbroyer/gwt-maven-archetypes/blob/master/guice-rf-activities/src/main/resources/archetype-resources/__rootArtifactId__-client/src/main/java/AuthAwareRequestTransport.java

But I'd be interested in seeing your code, particularly how you handle the feedback in this case (and what your "pipes" are about and how you use them); actually, I think I'd like to see a more complete sample, but I so much love digging into libraries' code that I'd like to see it too ;-)

Cheers

Sam

On Friday, July 12, 2013 9:24:32 AM UTC+1, Jens wrote:

Batching in RequestFactory can be done using RequestBatcher [1] and retries, as well as sending status events about pending requests, can be done by implementing a custom RequestTransport [2] for RequestFactory. Not sure if there is anything pre-implemented in case of the RequestTransport though.

[1] http://www.gwtproject.org/javadoc/latest/com/google/web/bindery/requestfactory/gwt/client/RequestBatcher.html

[2] http://www.gwtproject.org/javadoc/latest/com/google/web/bindery/requestfactory/shared/RequestTransport.html

-- J.

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