[twsocket] Future improvements for HTTP components?
This message is intended to start a dialog about future improvements to ICS components for Windows, in particular the HTTP client and server components where the world is moving ahead of us. Currently, new features tend to get added as needed by the main ICS developers for specific projects, for instance I've added cookie and better MIME support recently for my own projects. Other users have customised ICS components for their own purposes, sometimes submitting them as 'usermade' back to ICS, sometimes making them public in other ways. So the first question here is are new features needed for future Delphi projects using ICS, and if so what, in which order of priority? The next question is has someone done this work already, and are they prepared to donate the work to ICS for others to share? Finally, all this new stuff has to integrated and tested with the existing ICS code, which can be time consuming on it's own, so who can help? Usually that is those benefiting from the improvements? Specifically, for the HTTP client and server components: 1 - Support all the current requests, PUT, DELETE, PATCH, TRACE, OPTIONS and CONNECT, optionally. 2 - Support OAuth and/or OpenID authentication. 3 - Support Web sockets (not really HTTP), already done by Stan Korotky at http://ics-websockets.googlecode.com/svn/trunk Angus -- 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
Re: [twsocket] Future improvements for HTTP components?
Working, tested and elegant example or better if possible a reusable solution (some well written wiki on how to do it may suffice) of basic http server that handles requests but process them on different and configurable number of threads. Anyone? Thanks, Mauricio Enviado via iPad Em 25/06/2014, às 06:39, Angus Robertson - Magenta Systems Ltd an...@magsys.co.uk escreveu: This message is intended to start a dialog about future improvements to ICS components for Windows, in particular the HTTP client and server components where the world is moving ahead of us. Currently, new features tend to get added as needed by the main ICS developers for specific projects, for instance I've added cookie and better MIME support recently for my own projects. Other users have customised ICS components for their own purposes, sometimes submitting them as 'usermade' back to ICS, sometimes making them public in other ways. So the first question here is are new features needed for future Delphi projects using ICS, and if so what, in which order of priority? The next question is has someone done this work already, and are they prepared to donate the work to ICS for others to share? Finally, all this new stuff has to integrated and tested with the existing ICS code, which can be time consuming on it's own, so who can help? Usually that is those benefiting from the improvements? Specifically, for the HTTP client and server components: 1 - Support all the current requests, PUT, DELETE, PATCH, TRACE, OPTIONS and CONNECT, optionally. 2 - Support OAuth and/or OpenID authentication. 3 - Support Web sockets (not really HTTP), already done by Stan Korotky at http://ics-websockets.googlecode.com/svn/trunk Angus -- 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 -- 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
Re: [twsocket] Future improvements for HTTP components?
basic http server that handles requests but process them on different and configurable number of threads. Anyone? Have you looked at the existing threaded components and demos: OverbyteIcsWSocketTS.pas - Winsock component for building multithreaded servers OverbyteIcsThrdSrv.dpr - Basic multithreaded TCP server, banner sent in main thread OverbyteIcsThrdSrvV2.dpr - Basic multithreaded TCP server, banner sent in worker thread OverbyteIcsThrdSrvV3.dpr - Basic TCP server showing how to use TWSocketThrdServer Effectively, the existing HTTP server component needs OverbyteIcsWSocketS.pas replacing with OverbyteIcsWSocketTS.pas. I might look at this in a few months, since my own web server is currently blocking for a few milliseconds while SQL requests complete, but no-one has ever complained. Angus -- 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
Re: [twsocket] Future improvements for HTTP components?
Date: Wed, 25 Jun 2014 14:21:00 +0100 From: an...@magsys.co.uk To: twsocket@lists.elists.org Subject: Re: [twsocket] Future improvements for HTTP components? basic http server that handles requests but process them on different and configurable number of threads. Anyone? Have you looked at the existing threaded components and demos: OverbyteIcsWSocketTS.pas - Winsock component for building multithreaded servers OverbyteIcsThrdSrv.dpr - Basic multithreaded TCP server, banner sent in main thread OverbyteIcsThrdSrvV2.dpr - Basic multithreaded TCP server, banner sent in worker thread OverbyteIcsThrdSrvV3.dpr - Basic TCP server showing how to use TWSocketThrdServer Effectively, the existing HTTP server component needs OverbyteIcsWSocketS.pas replacing with OverbyteIcsWSocketTS.pas. I might look at this in a few months, since my own web server is currently blocking for a few milliseconds while SQL requests complete, but no-one has ever complained. Angus -- 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 -- 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
