RE: [wsrp] spec-2.0-draft05: lifetime interfaces: allow Consumers torequest life timeon creation?

That's what is under discussion. However, when coding a consumer, one
must still check that the value returned is similar to that requested
(so this is only a potential optimization) and a producer is likely to
only agree to consumer values close to their default policy or SLA, and
if the consumer should ask for a value significantly different, I would
*still* return the default and force the consumer to do the extra work
of setting the lifetime:

Consumer "Can I have 5 please"
Producre "Only if you can't make do with 3"
Consumer "No, I really need 5"

Producer "OK, then I will make special arrangements to provide you with
5, such as set extra timers, etc."

Therefore, the optimization may not be worth much.

Regards,
Andre

-----Original Message-----
From: Richard Jacob [mailto:] 
Sent: 04 March 2005 11:38
To: 
Subject: [wsrp] spec-2.0-draft05: lifetime interfaces: allow Consumers
torequest life timeon creation?

Currently the only way for a Consumer to set a lifetime is to use the
lifetime interfaces.
This requires additional roundtrips once a Context (Registration or
Portlet) is created.
Shouldn't we allow Consumers to request a lifetime (and refreshDuration)
when creating new instances on the Producer?
I.e. add a lifetime request to register(), modifyRegistration() and the
PortletManagement clone/copy/import operations?
In that case we would also need a lifetime request whenever implicit
cloning is requested (pbia() and handleEvents() with "cloneBeforeWrite"
set).

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Standardization Technical Lead
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:


---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: