Well I haven't used OnRequestEnd, but I would presume that if your using it
in a <broadcasts> statement, then it would actually be executed before any
<views>
I think all <broadcasts> get executed, then all <views>, then all <results>,
doesn't matter about their <before> and <after>'s as it relates to those 3
tags, internally, a <before> broadcast happens before an <after> broadcast.
But an <after> broadcast happens before a <before> <view>.
My solution is only a work-around, not an actual OnRequestStart. If you
want a OnRequestEnd,
I suggest moving the call in the Remote type from <broadcasts> to <results>
IE, make an event-handler like so
<event-handler name="OnRequestEnd" access="private">
do your OnRequestEnd stuff here, broadcasts, etc stuff you want done last
</event-handler>
Then in the Remote event-type, do this...
> <event-type name="Remote">
> <before>
> <broadcasts format="remote">
> <message name="OnRequestStart" />
> </broadcasts>
> </before>
<after>
<results>
<result do="OnRequestEnd" />
</results>
</after>
</event-type>
Since results are run last, and an after result last of all (unless other
after's are added after), it should run after the view is rendered.
--
Chuck Savage
http://SeaRisen.com
--
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en
