Upcoming Change to Remoting Request Lifecycle
Ezra Parker
release is a change to the internal execution of remoting requests. At
the present time, a remote request will execute only the targeted
event-handler in an isolated fashion, meaning that none of the
internal events that normally execute within the lifecycle of a
standard Model-Glue event are fired.
The Model-Glue team feels that this is a bug, and therefore we're
intending to alter the processing of remoting requests so that they
are handled in the same manner as standard events. This means that the
full range of built-in event-handlers and their corresponding
broadcasts will be run. From the standpoint of message broadcasts,
once this change is made a remote request will now broadcast the
following messages:
onApplicationStart (when relevant)
onSessionStart (when relevant)
onRequestStart
onQueueComplete
onRequestEnd
(For anyone wondering about onSessionEnd, as this is completely
decoupled from the event lifecycle, its behavior will not change -- it
is fired whenever a session ends.)
Also, all of Model-Glue's internal phases will now be run by a remote
request, meaning that an application will be initialized/reloaded as
necessary, and event value population will also occur.
As this modification will have the potential to break existing
applications that leverage the remoting feature, we wanted to
publicize this impending change, and solicit feedback from anyone who
might feel that this not a wise idea. If you have an existing
application that would be adversely impacted by this change, or have
any other comments, please let us know.
--
Ezra Parker