Why not build VOS layered on top of HTTP, XML-RPC, SOAP, BEEP, CORBA, or some other existing system?
If necessary, VOS could be tunneled over any of these transports, or an adapter or bridge service could connect a VOS system to another existing system. However, because we have our own object model, message format, and network transport protocol, these standards wouldn’t buy VOS itself anything. In fact, a single-stream based system like HTTP (and therefore XML-RPC, SOAP, etc.) actually can prevent a VOS system from performing acceptably in an interactive multi-client environment.
Related Questions
- Page 55 of 137, third paragraph: If the existing interim shoulder is wide enough, the HTC system may be placed in the existing paved shoulder . What is wide enough?
- Why not build VOS layered on top of HTTP, XML-RPC, SOAP, BEEP, CORBA, or some other existing system?
- Does the online system have the same data requirements as the existing paper system?
- Does the online system have the same data requirements as the existing paper system?
- Can I install a geothermal heating system in an existing home?
- Can I install a geothermal heating system in an existing home?
