rstudio / r-websockets Goto Github PK

Hi guys,

we are currently using this great package in one of our projects. I just wanted to give you guys a heads up that this also applies to the R-Websockets package. It caused us quite a headache seeing as it results in some quite unpredictable behaviour (server suddenly starts responding after X calls to it and so on...).

Hope it is ok that i posted it as an issue

regards

Raphael

An opposing function to createContext that shuts down the server socket and cleans up (kills) all client connections would be handy to have...

Hey there,

I just stumbled upon this package (great job btw!) as I need some websocket functionality in R.
However, the package -- as it is in git HEAD -- doesn't work OOTB with modern chrome releases (got Chrome 14 beta here).

The newest libwebsocket git HEAD, however, does support rev 7.
Between rev 7 and rev 8 there were no real changes done to the protocol itself (I believe) therefore, it can easily be hacked into working with rev 8, too :)

Would be great if you could add support for rev 08 out of the box!

Hi,

I have a shinyapp that requires transfer of large json data. I am new to this world so please pardon my ignorance. I have read that compression of data while transfer using websocket can speed up my app significantly. Was wondering if R websocket natively support compression of json while transferring to and from the client or do we need to make some tweaks to enable it.

Regards
Sushanta

I have cloned the repository this morning to my machine, built it with R CMD build R-Websockets/ and installed it with R CMD INSTALL websockets_1.1.0.tar.gz

When running any of the demo scripts, as soon as a client connects I get the error:

Error in !is.na(server$DEBUG) && server$DEBUG : 
  invalid 'y' type in 'x && y'

traceback() gives:

> traceback()
1: service(w)

And sessionInfo() returns:

> sessionInfo()
R version 2.13.1 (2011-07-08)
Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit)

locale:
[1] en_GB.UTF-8/en_GB.UTF-8/C/C/en_GB.UTF-8/en_GB.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] websockets_1.1.0 digest_0.5.1     caTools_1.12     bitops_1.0-4.1  

Section 5.5.2 of RFC 6455:

Upon receipt of a Ping frame, an endpoint MUST send a Pong frame in
response, unless it already received a Close frame.  It SHOULD
respond with Pong frame as soon as is practical.  Pong frames are
discussed in Section 5.5.3.

Looks to me like this needs to go at the end of the service function in websockets.R.