W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

Issue 012: EPR Lifetime

From: Bob Freund <Bob.Freund@hitachisoftware.com>
Date: Wed, 3 Nov 2004 07:39:40 -0500
Message-ID: <3587D6FDF44881459313970A8DE75A8101B68D92@exchange.quadrasis.com>
To: <public-ws-addressing@w3.org>
 

Statement of issue:

At the moment there is no specification of the lifetime of an Endpoint
Reference.

What needs to be decided is:

1)       Is there a need to provide a mechanism for management of EPR
lifetime? If yes then what should it do?

2)       Or: Is there a need to make some statement concerning an
implied EPR lifetime? If yes then what?

 

Arguments Against:

1)       The web has gone well enough up to now with the tacit
assumption that uri's live forever.

2)       There is nothing like a 404 to indicate that the EPR you seek
has gone missing. The service thus has complete control over expiration.

3)       Much complexity especially in request-response MEPs. A lot of
this complexity will arise from treatment of the case of EPRs expiring
between receipt of request and receipt of response.  This complexity
will extend to further complicate all protocols that permit the use of
EPR expiration.

 

Arguments in Favor:

1)       Provides a handy way for the EPR minter to control cache
contents.

 

 

 

General Puzzlements:

1)       Would EPRs compare equal if their expiration times were not
equal?

2)       If one received a message with an expired EPR in its to:, whan
ought it to be dropped?

3)       If one received an expired EPR in its replyto: ought the
message be discarded?

 

 

  

 
Received on Wednesday, 3 November 2004 12:40:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:59 GMT