Re: [MirageOS-devel] Cohttp, and the SSL saga update

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

On 04/19/2014 21:27, Anil Madhavapeddy wrote:
> The JSON you're transmitting in each chunk is incremental.
> Shouldn't every response chunk be standalone parseable?
> 
> Also, I'm not sure that this sort of long-lived connection will
> work outside an Javascript request, since the client will be
> buffering and waiting for a 0-length chunk for the end of the
> connection.  Chrome is probably just waiting rather than doing an
> incremental rendering.  If you stick some Javascript on /watch and
> try a long poll it will probably work better.

There's also a server-sent events extension defined by w3, which I'd
use for this purpose: http://www.w3.org/TR/eventsource/


happy hacking,

hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJTUtBMAAoJELyJZYjffCjuWxgP/3Yx/8XOod/WkNpu2YDYMqwN
FM3ixer9X4kbegp+sUOXzJXQmRnrVdY7kQHyd1ZCEt2YNtlBoOd4Q3SRSCB2rGm+
uBcqbrnCBUuzkmtsGI68SzSHMqSjiq2sI2NVjlmTCYxpJthLJ23mAbRr0//NbdJV
iUOTPKCdOqFFjp1Hg31UYHNt+FIAKejzXbLqIV1X63coKChlmy5o5YqyQV77271o
s9GgCWQl2OmWVFH0NnA+YXoQ5MTeTW3dVbpgWGha79G3Y//TATIrMWjm+QDEE21l
+cI+Bjc9vsLoXXTMGoXO1NCUcqu5wAFkHjhqOX5aadMg/Ix98kTE99glEwBmVBYb
+xALH9cRn8/XkWGD9EYnwD5651/kfOOXP5I+FRL/KYgps9eCS9ggOvypLlDFj2Zq
TDkqmoKLvOi+43qAZUb/cy819+UfNFYtpjUqA2HErC3QH0Bf+c8vF6epC6vmvvm4
gStYm7Qsju3NJ/oO+Ly0QYxUSkdv1OLIMuLOwXbxTHvVfDeMH07KWJcly+XqonV7
2JsgNwyHxn5hjKpcuw8pHmN/UayoDxDXWu1Y7gRtzmdqbbmQvxgfxWs08NLnlepp
Z61d1MuyCurkerHvmuB8PwOfppLN0iQ+z4fPe1JaNTSJw+Ql6YBDJysSNGeC4NSm
RIXjA4DuwdoXlfwe3i5Z
=SDZY
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel