I recently wrote an article for Comet Daily that was a proposal for a standards based approach to comet communication. One of the key components of the proposal that made it go, was the mechanism for using standards to coherently subscribe and respond to multiple resources. By applying the multipart/digest content type to HTTP messages, multiple HTTP messages can be wrapped up in single message using a standard MIME type. In the MIME type specification, the multipart/digest is defined in the context of email messages as being a container for multiple email messages. However, it does not take too much imagination to infer that when this content type is used in the context of a HTTP messages, that the content would be a multipart message composed of multiple HTTP messages.
While there are certainly client/server frameworks out there that support Ajax batching (such as DWR), they alll do so with their own internal protocol. Using the multipart/digest content type opens the door for batched Ajax requests with an open protocol that would allow client libraries to send batched requests to various server side components. I will try to create a client library that will modify the XmlHttpRequest object to support batched requests using this technique.
June 20, 2013 at 10:49 am
Car shopping is something which almost all adults will face in their
lives. If you want to drive, you’ll have to buy yourself a car. The simple ideas below will help you turn the car buying process into something you not only can handle, but that you are a master of.