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 with requesting each 
 portion of data by separate http-request. WebSockets allow you to do the
 same without overheads on HTTP-headers, which may be very large in 
 comparison with your data, if you're exchanging with small data elements.

OK, I understand. You want to support existing client. Sounds good to me.

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.

If you don't know that component yet, have a look at the [unfinished]
tutorial : http://wiki.overbyte.be/wiki/index.php/TutWebAppServer

--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be




--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


[twsocket] HttpCli, state Ready ?

2012-03-05 Thread Bruno Mannina

Dear,

Can I use the property Http.State=Ready for consider that the http 
component is fully available and its last download is finished?


Many thanks,

Bruno
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be