>> What will be the mechanism to allow pass-thru for
non-user-initiated
>> async calls? Calls where user navigation is irrelevant, like a
>> background, timer-based call to collect information or perform some sort
>> of task? WIll there be a way to somehow tag the call as being
>> untouchable? Or perhaps another callback method outside of onSuccess
>> and onFailure, like onContextChange?
> The only non-user-initiated call that is outside the context of a
> particular view that we could think of is the background call that
> periodically updates the alert count at the top of the page. Although
> calls to periodically auto-refresh portlets or other data in the current
> view are technically non-user-initiated, they are still in the context
> of a particular view and so could still be assigned a tracking uuid.
I'm not 100% sure but we may have some stuff going on in the session
manager code.
I see UserSessionManager.refreshHttpSession() which periodically hits
portal-war to keep its session alive, but it doesn't go through one of
our GWT RPC proxies to send the request, so we probably don't have to
worry about it.
In any case, if we do find some other RPC calls that are outside the
context of a particular view/navigation, then I guess we can add a way
for the user to specify that the uuid stuff should be skipped when
requesting a proxy instance from GWTServiceLookup., e.g.:
boolean skipViewUuid = true;
FooGWTServiceAsync fooService =
GWTServiceLookup.getFooService(skipViewUuid);
>> Related, although I'm not sure this is really a valid use
case, it may
>> be required thata use-initiated call must have its callback invoked even
>> if there is a context change. For example, the async callback may need
>> to itself invoke some sort of callback or listener on its completion.
> That's a good point. One example I can think of is calls that update
> something on the Server side (e.g. uninventorying a Resource or creating
> an alert definition); ideally we'd still want to display a message
> informing the user the operation had completed, even if the user had
> navigated to a different page while the call was in progress. If we
> short-circuit the call to onSuccess() or onFailure(), we won't be able
> to display such a message...
Does anyone have any thoughts on how we should deal with this?
>