Subject: Re: EntityProxy efficiency
One .fire() equates one HTTP request. You can .append() request contexts,
but then only one of them can be fire()d (you'll have an exception
otherwise).

Otherwise, yes, one session will have several transactions, possibly
unrelated, but that's the whole point of "batching" things in a
RequestContext in Request Factory; and AFAICT it doesn't matter much wrt
JPA (on the contrary, the goal of sharing the session is to share its
entity cache so that your isLive calls could be possibly be cheap).

--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/4Gw6f7s0B7AJ.
To post to this group, send email to google-web-toolkit@xxxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
google-web-toolkit+unsubscribe@xxxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.

(C)2011 mailinglist-archive.com