OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bt-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [bt-spec] FW: Issue 89


Hi everyone,

I've just read Geoff's document and Mark's comments. Now I am perfectly
willing to accept that I might be being naïve here, but could someone please
clarify for me what precisely the benefits of sharing state in a common
format are? I can well enough see the drawbacks for myself, but I am rather
finding the benefits difficult to quantify.

I don't have an objection to J2EE (or any other platform for that matter)
interop with BTP, but does sharing of state (as opposed to say defining
standard bindings at the message level) really achieve that objective in a
straightfoward way?

Again, this isn't a rebuttal to the Oracle/Choreology suggestion, more of a
plea for help in understanding its value.

Ta.

Jim


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC