Great!
On Fri, Jun 18, 2010 at 5:43 AM, Ludwig Schwardt
wrote:
> Hi,
>
> On Thu, Jun 17, 2010 at 6:30 PM, Ondrej Certik wrote:
> > That would be exactly what I need. Do you have any time frame for the
> > release? The problem is that I need it right now. So I'll try to
> > finish my own stuff to
Hi,
On Thu, Jun 17, 2010 at 6:30 PM, Ondrej Certik wrote:
> That would be exactly what I need. Do you have any time frame for the
> release? The problem is that I need it right now. So I'll try to
> finish my own stuff today, so that I can at least work and then later
> improve it or switch to yo
Hi William,
We are using the HTML5 websocket as proposed in
draft-hixie-thewebsocketprotocol-75. This is supported by Chrome 4/5
and now Safari 5. This standard is evolving and Chrome 6 onwards will
be using draft-ietf-hybi-thewebsocketprotocol-00 which simplifies the
syntax somewhat but does brea
I would be interested in seeing the screencast. For the websocket, are you
using "Comet" (which is what we use for our live data through the used of
orbited and STOMP, so I could see being able to do interactivity, but
thought it would be too slow for interactivity, which is why we went with
FLOT
Hi,
On Thu, Jun 17, 2010 at 8:07 PM, william ratcliff
wrote:
> How do you deal with interactivity?
When you create a figure, a WebSocket server is spawned on its own
socket, with its own thread. The client (browser) then interacts with
these threads. Zooming, panning and resizing are all done on
