Why is all XWT communication procedure-call based and HTTP-driven?
Serializability Unlike most programming environments such as Java and .NET, XWT has the property that no script can ever make a nonserializable object (such as Java’s java.net.Socket, java.lang.Thread, java.awt.Window, or java.lang.Class). This means that at any time, the entire state of an XWT app can be serialized and shipped back to the server to be restored later, without requiring any additional effort from the application developer. By limiting network connectivity to procedure-call based transactions, this property is maintained. If long-lived socket connections were allowed, XWT apps would not be serializable, because open sockets cannot be serialized. Proxy Compatability Those of us fortunate enough to have packet-level access to the Network often forget that most of the world is trapped behind a corporate proxy. For those people, HTTP is All There Is. To ensure that XWT works for these people, and, more importantly, to ensure that all XWT apps are guaranteed to work in all en
