ASOs are specified in terms of implementation classes, not interfaces.
That makes it more awkward and error prone to create a proxy for them
(you have to create a subclass and hit all the non-private methods and
make them delegate, and there can be issues concerning constructors
that get in the way
Also, maybe you should be using ConcurrentHashMap or other classes
specifically made for multi-threaded access. And if you review the
javadoc for that class, I think they discuss how they handle iterators
in a multi-thread safe manner..
Howard Lewis Ship wrote:
Does raise an interesting poi
> So it does seem to me that if you are using Ajax techniques and thus
> explicitly asynchronous access to the application, you should be
> mindful of this. We could bounce around some ideas as to how the
> framework could assist: perhaps a per-session/per-page lock?
A per-session/per-page lock
Does raise an interesting point.
In a traditional page app, you would rarely have request overlap. It
was possible (a wildly clicking user, perhaps). Often the main page
would be one request, followed by a series of overlapping requests to
retrieve static assets.
It would be possible to add a f
On one page I use a persistent Hashmap. The page contains an actionLink
with a click event handler. The onclick event is activated with a delay
using setTimeout. When the event is fired another actionLink is
activated. Now what happens is that during the handling of the first
actionLink the second
