![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Christian Huitema wrote: > > > christian - i'd like to understand any technical concerns you might > > have on the "soap over beep" specification. > > Well, I am mostly concerned to see "SOAP over BEEP" defined before we > define the alternative "SOAP over TCP". I mean, if we are transporting > opaque blobs of data between two points, TCP looks like a no-brainer... There are other "SOAP over foo" proposals in the wings too. I do agree that the general question needs looking at. Maybe it's OK to have lots of SOAP mappings, or maybe it isn't. Although mtr may disagree, imho this does need to be considered before deciding to publish a Proposed Standard. Brian
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.