Which would you recommend? Btw, I do want the socket to be capable of supporting both client and server sockets.
Regards KK On 11 April 2013 17:58, Murphy McCauley <murphy.mccau...@gmail.com> wrote: > There have only been a few users of the modern (betta) version, AFAIK. But > the messenger component is specifically JSON-oriented. If you want to do > binary messages, you can: > > 1) Write a plain old socket server thing that runs on another thread (i.e. a > select() loop) and interacts with the coop Tasks. The web stuff works this > way. > 2) Write a recoco-friendly cooperative socket server thing that runs in its > own cooperative Task (i.e. a yield Select() loop, like of_01) > 3) Use the lib.io_worker IOWorker abstraction (basically a wrapper around #2) > > -- Murphy > > On Apr 11, 2013, at 5:46 PM, kk yap wrote: > >> Hi, >> >> Has anyone actually used messenger.TCPTransport? My goal is to handle >> TCP connections with binary messages. So, I am hoping that I can >> reuse this component. >> >> Any advice is appreciated. >> >> Regards >> KK >
