[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp] Request scope support
Both request and reply messages may be
dropped by the network (e.g. some proxy in a forwarding chain). The resulting uncertainty
about the state of a action/event/render cycle implies that a producer could at
best communicate it’s intention to initiate a new cycle (e.g. via a monotonically
increasing counter rather than a boolean). Having missed the call, I’m
not clear on the benefits (if any) this would bring. At best a consumer could
tell if it had recently seen an action or event the producer associates a
render request (having the same producer set identifier) by keeping recent action
(ids) in a consumer side cache? What about leveraging the existing ability
to return markup from actions and events? At least this allows two phases (not
three) to be collapsed. Here, events become a sort of “action” that
(like actions) result in a new (consumer) cacheable rendering. Of course, this
implies that producers don’t just throw away such markup returns and that
all events are independent of action request values. That may be a
recommendation we should make (always make events independent of the initiating
action)? Regards, Andre From: Rich Thompson
[mailto:richt2@us.ibm.com]
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]