[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: RM Group Definitions
we have our hand full at the moment.. i strongly suggest we table this one until 1) ms spec is done, 2) security spec is in draft, 3) rm is in draft, 4) requirement spec is updated,.... so that we can have stuff in place for nick's team... soonest... so unless i hear a large nay from the a majority of the team, lets get off of this subject for the short term.... best regards, rik -----Original Message----- From: David Burdett [mailto:david.burdett@commerceone.com] Sent: Tuesday, August 29, 2000 2:53 PM To: 'Christopher Ferris'; richard drummond Cc: ebxml-transport@lists.ebxml.org Subject: RE: RM Group Definitions Application level specifying a "grouping" might be business requirement as an application might not want to send out a message until it **knows** that an earlier message has been delivered. In this case, the application / business process would have to let the messaging service know when to end a "group". David -----Original Message----- From: Christopher Ferris [mailto:chris.ferris@east.sun.com] Sent: Tuesday, August 29, 2000 6:43 AM To: richard drummond Cc: ebxml-transport@lists.ebxml.org Subject: Re: RM Group Definitions I agree. It isn't clear to me where the notion of BP-level or application-level grouping came from as I haven't had an opportunity to read ALL of the messages sent during my vacation, but this seems to me to be something we should steer well clear of. Chris richard drummond wrote: > > i don't see grouping messages as being a key point of a reliable messaging > spec. yes it is important for performance... but not for reliable messaging. > that is why i think we should forgo it on this round and concentrate on the > rm part of things.... best regards, rik > > -----Original Message----- > From: Jim Hughes [mailto:jfh@fs.fujitsu.com] > Sent: Tuesday, August 29, 2000 3:41 AM > To: ebxml-transport@lists.ebxml.org > Subject: RE: RM Group Definitions > > Then we need to come to a quick resolution on this point in the group. If > message grouping (by this I mean sending only one MSH-level ACK for a group > of reliable messages) is not allowed, then it greatly simplifies the RM > spec... I suggest we carefully consider this before taking the decision for > this level of simplicity may yield an unacceptable solution. > > Jim > > At 03:47 PM 8/28/2000 -0500, richard drummond wrote: > >i don't think grouping is appropriate at this time. we need to keep it > >simple for the first round of ebxml... that is that though the end of may > >next year..... rik -- _/_/_/_/ _/ _/ _/ _/ Christopher Ferris - Enterprise Architect _/ _/ _/ _/_/ _/ Phone: 781-442-3063 or x23063 _/_/_/_/ _/ _/ _/ _/ _/ Email: chris.ferris@East.Sun.COM _/ _/ _/ _/ _/_/ Sun Microsystems, Mailstop: UBUR03-313 _/_/_/_/ _/_/_/ _/ _/ 1 Network Drive Burlington, MA 01803-0903
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC