How do you process that data on the client side given the poor support of ArrayBuffer and Blob?<span></span><br><br>On Monday, June 18, 2012, Corbin Simpson wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Jun 15, 2012 at 12:32:37PM -0700, Glyph wrote:<br>
> On Jun 15, 2012, at 10:13 AM, Laurens Van Houtven wrote:<br>
> > The issue is that while AMP is inherently a binary protocol, WebSockets transfer text (well, that's a lie: there's a binary version, but it's even less widely supported than WebSockets themselves -- and SockJS doesn't support it at all, although it's on the roadmap). So, I need an alternative, preferably 7-bit, serialization for AMP boxes.<br>
> Did you immediately discard the obvious solution of "base64 everything"? :)<br>
<br>
I should point out that at least one WebSockets JavaScript thing, noVNC, uses<br>
base64 as its solution to the problem, and that's what I originally wrote txWS<br>
to deal with. This works quite fine for OSUOSL on all of the target browsers<br>
we care about.<br>
<br>
I don't know if this is the *right* solution, but it certainly is the least<br>
painful.<br>
<br>
~ C.<br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'Twisted-Python@twistedmatrix.com')">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</blockquote><br><br>-- <br>cheers<div>lvh</div><br>