+1, although I don't think (a) is necessary.
On Jan 13, 2004, at 6:36 PM, noah_mendelsohn@xxxxxxxxxx wrote:
I really want to maximize interop of the HTTP bindings, and
minimized the code that's required to achieve such interop. Since
HTTP is
binary-clean in any case, allowing variability there would just require
extra code in conforming implementations, more interop testing, etc.
In
practice, I would expect interop to be reduced. So, I would either
disallow variability everywhere, or allow choice of binary, not text,
representations in Miffy and (a) state in Miffy that each application
of
Miffy must specify the allowed encodings allowed and (b) allow only
binary
in the http binding.
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
