> > My take is that HTTP's strength is text, and that we'd want to be able > to compress any generic text well, perhaps starting with a common > dictionary > of HTTP tokens (GET etc.) for the text compressor. > > food for thought/discussion in Stockholm? >
HTTP-DTN looks really interesting. I especially like the store-forward model and Content-Source and Content-Destination headers. One troubling aspect of Chopan is how to handle PUT/POST to a sleeping nodes. Perhaps a store-forward model might be a better fit than trying make it a caching model? The idea of using a common dictionary for compressing any text (including maybe even the body) might be really interesting. The beauty of HTTP is that provides a transport for any MIME typed data, so we can pass binary data, text data, or new versions of compressed data. For me, the open ended nature of how a resource is represented on the wire is the most compelling aspect of HTTP.
_______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
