Hi,
Its nice but as you said its a slightly different context. Of course I can
integrate some place information into my RPC mechanism but that does not
solve the problem that if n activities get started in parallel each one will
do a server request and each one will get a "not authorized" error
Hi Jens,
we've had some similar question in a different context: how to
determine the first request per place.
our idea is pretty simple, therefore i guess its a good one ;) (we're
using restygwt, so my terms might differ somehow from the native gwt-
rpc):
* requestdispatcher is a placechangehan
Hi,
during place integration I was thinking about activities and
authentication/authorization. Authentication seems pretty easy as its done
outside the whole places/activities framework but what about authorization?
Lets say someone has bookmarked an URL like /#/editcustomer/123 because this
p
