Hi
While discussing the cons of Comet on Comanche I noticed that Andreas
actually implemented WebSockets for WebClient. I went on and wrote a
small wrapper around it for Seaside.
What you need:
- The very latest Seaside-Canvas and Seaside-HTML5
- The latest WebClient, if you're on Pharo you need the attached one
- Seaside-WebSocket-Core, Seaside-WebSocket-WebClient,
Seaside-WebSocket-Examples from [1]
- Crhome, Firefox 4 or Safrai 5
- start the WAWebServerAdaptor on port 8080
- go to
http://127.0.0.1:8080/websocket/chatThe important class is WAWebSocket which is an abstraction over a
WebSocket. Since WebClient is the only Smalltalk implementation of
WebSockets I'm aware of the protocol is modeled after it. There are
supposed to be web server specific subclasses / adaptors like
WAWebClientWebSocket. A new WAWebSocket is created with a server
specific factory object (WAWebSocketCreator) in the request context. I
want to say is you get a new WAWebSocket with:
aRequestContext newWebSocket
And yes, that stuff is experimental as you'll note from the stack
traces in the Transcript.
[1]
http://www.squeaksource.com/Seaside30AddonsCheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev