[BXXPwg] SOAP over BEEP

Bill Mills wmills@invisibleworlds.com
Mon, 18 Jun 2001 12:09:02 -0700


I had not asked this before, but does this indicate that the algorithms
currently in use do not conform to the RFC per se?  Admittedly we fall into
the vague <schem name>:<opaque scheme specific part> type of construction.

-----Original Message-----
From: Eamon O'Tuathail [mailto:eamon.otuathail@clipcode.com]
Sent: Saturday, June 16, 2001 9:47 AM
To: bxxpwg@lists.invisibleworlds.com
Subject: [BXXPwg] SOAP over BEEP


>> Why not use something similar to the JDBC URLs in Java:
>>
>>  beep:tcp
>>  beep:tcp:ssl
>>  beep:sctp


As Roy says at:
http://lists.invisible.net/pipermail/bxxpwg/2001-June/000523.html

"You have no idea how many systems you would break simply by choosing
   beep:soap://example.com/
over
   soap.beep://example.com/

They may seem the same, but the first requires an algorithm change in
every deployed piece of Web software, whereas the second just requires
the addition of a plug-in handler."

_______________________________________________
BXXPwg mailing list
BXXPwg@lists.invisible.net
http://lists.invisible.net/mailman/listinfo/bxxpwg