[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia][wsrp-interfaces] expires as a timestamp rather than an int
The timeout with a timestamp seems like a good and easy solution for this. It should make it loggable for troubleshooting. At 4:45 PM -0700 7/15/02, Alan Kropp wrote: >I don't understand what a timestamp accomplishes on its own. The same >network latency that eats up the timeout could overtake the timestamp, and >then what is the Producer supposed to do? Maybe it should be a timestamp >_and_ a timeout? > > >-----Original Message----- >From: Rich Thompson [mailto:richt2@us.ibm.com] >Sent: Monday, July 15, 2002 10:58 AM >To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org >Subject: [wsia][wsrp-interfaces] expires as a timestamp rather than an >int > > > >expires was originally proposed with a type definition. I would agree that >a timestamp would be better than it actually referring to a duration. > > > > > > "Tamari, Yossi" > > <yossi.tamari@sap To: >wsia@lists.oasis-open.org, > .com> >wsrp-interfaces@lists.oasis-open.org > cc: > > 07/15/2002 12:47 Subject: RE: >[wsia][wsrp-interfaces] Refactoring the data objects > PM > > > > > > > > > >See my comments marked with [YT]. >(Most of them are in appendix A, since it seems appendix a is the real >definition of the spec, which I think is wrong, and is a result of what >Rich mentioned below about the obscurity of the interface.) > >The endless debate about putting WSIA concepts in the WSRP standard is >still there... > > Yossi. > >-----Original Message----- >From: Rich Thompson [mailto:richt2@us.ibm.com] >Sent: Friday, July 12, 2002 9:09 PM >To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org >Subject: [wsia][wsrp-interfaces] Refactoring the data objects > > >As requested in Tuesday's Joint interfaces call, I have reworked the draft >spec in an effort to factor the data items into the scopes presented at the >June F2F. Personally I think this obscures too much and that some of the >data items should move up to first class parameters in the interface. >Hopefully this version can provide a reasonable basis for a discussion of >which items should be promoted either for clarity or as part of supporting >any factoring of the operations. > >Technical note: In order to make this readable but yet leave an indication >of what was modified, I accepted the changes and then appended a space on >the end of changed lines so that a change bar will appear on the left. So >much changed in Appendix A that it all should be considered modified. > >(See attached file: WSIA - WSRP Interface Specification.doc) > > > > >#### WSIA - WSRP Interface Specification1.doc has been removed from this >note on July 15 2002 by Rich Thompson > > > > > >---------------------------------------------------------------- >To subscribe or unsubscribe from this elist use the subscription >manager: <http://lists.oasis-open.org/ob/adm.pl> > >---------------------------------------------------------------- >To subscribe or unsubscribe from this elist use the subscription >manager: <http://lists.oasis-open.org/ob/adm.pl> --
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC