Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-18 Thread Stan
- From: Fredrik Larsson To: 'ICS support mailing' Sent: Friday, March 16, 2012 4:08 PM Subject: Re: [twsocket] Design principles of WebSockets server for ICS Hi, I would be very interested in trying out and test this websocket-component. I don't think that there is a huge need for a Delphi-client

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-16 Thread Fredrik Larsson
another usage.. Regards, Fredrik. -Original Message- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of François Piette Sent: den 4 mars 2012 16:25 To: 'ICS support mailing' Subject: Re: [twsocket] Design principles of WebSockets server for ICS By the way, I

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-06 Thread Stan
Hi Francios, To go back to your initial design question, it is probably better to start with the THttpAppSrv component which is by far the most advanced one to build dynamic web application backend. As the THttpAppSrv is a decendant of THttpServer, it requires the same or even larger amont of

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-05 Thread François Piette
By the way, I don't really understand the real world use case for such WebSockets in the context of a IC/Delphi/WebServer application. Unless you have to support and existing client application, it is IMO not very interesting. Maybe I'm wrong. The websockets supersede the old AJAX approach

[twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread Stan
Hi Everybody, I have a WebSockets server based on ICS. It is currently implemented as a tcp-server (TWSocketServer without any modifications) with custom descendant of TWSocketClient, which provides all necessary functionality for WebSockets handshaking and data exchange. We could use it in ICS

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread Angus Robertson - Magenta Systems Ltd
I think, this is only possible if the current THttpServer component (actually, meaning with the THttpConnection component) is extended and reworked. That is deriving new components from the existing ones will require overriding of most important virtual methods and copy-pasting much of

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread François Piette
://www.overbyte.be -Message d'origine- De : twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] De la part de Stan Envoyé : dimanche 4 mars 2012 16:09 À : ICS support mailing Objet : [twsocket] Design principles of WebSockets server for ICS Hi Everybody, I have a WebSockets server

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread RTT
On 04-03-2012 15:24, François Piette wrote: I don't really understand the real world use case for such WebSockets in the context of a IC/Delphi/WebServer application Now that web browsers are implementing it (http://en.wikipedia.org/wiki/WebSocket#Browser_support), it would be nice to have

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread Angus Robertson - Magenta Systems Ltd
Now that web browsers are implementing it (http://en.wikipedia.org/wiki/WebSocket#Browser_support), it would be nice to have support for it from ICS too. OK, so this is just server push under another name. To implement either the client or server using ICS, we need the opposing client and

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread Stan
Hi Angus, Now that web browsers are implementing it (http://en.wikipedia.org/wiki/WebSocket#Browser_support), it would be nice to have support for it from ICS too. OK, so this is just server push under another name. You are wrong, because this is not just another name of the server push,

Re: [twsocket] Design principles of WebSockets server for ICS

2012-03-04 Thread Stan
Hi Francois, As I understand, you are trying to - or you already have - implement RFC6455, server side (http://tools.ietf.org/rfc/rfc6455.txt). Is that correct ? You are right, but we code supports both hixie and hybie protocols. By the way, I don't really understand the real world use case