Thread View: borland.public.cppbuilder.internet.socket
3 messages
3 total messages
Started by Colin B Maharaj
Wed, 02 Apr 2008 21:46
Proper HTTP Support
Author: Colin B Maharaj
Date: Wed, 02 Apr 2008 21:46
Date: Wed, 02 Apr 2008 21:46
50 lines
2823 bytes
2823 bytes
2 questions ----------- Hi folks, here is my story. In the last few years, I have developed an application that needed to get HTTP support. The fact is that it is a large application (for one person to create at least) and adding web support was a bit confusing initially. Then I came across an article that allowed me to put in a web server right in my application. This was in BCB 3. Then I moved to BCB 6 (and Indy9) and used the same code except with Indy Server sockets, then added HTTPS using the SSL components. Note: I did not use the HTTP Server component that came with Indy9. And I am thinking of moving to Indy 10. Then, in the last few months I have been able to add HTTP Deflate using the ZLIB Library at http://www.zlib.net/ and what seem to be an unsupported TZlib C++ wrapper by Richard W. Frost. And I just added support for If-None-Match: and return code 304 for caching images and CSS files in particular. The last two were important in terms of features for lowering bandwidth usage in my customers network. Question 1.(Finally) If I move to Indy10 and the HTTP Server lock, stock and barrel, will I be getting SSL, Deflate and If-None-Match/304 support in the server or will I have to do it all over again using Indy10 server components. Question 2. I saw a brief description of Indy10 support for 'A' as in WSA Asynchronous support and claiming to be better supported for many thousands of connections. But I remember years ago I saw (heard) (cannot remember) that Indy is based on blocking server technology for it implementation so that each connection has to be managed in it's own thread and so on..... What's the story with this, should I go with indy10 new super core structure or stick with the blocking model. Thanks anyone for being patient enough for reading this... Colin B Maharaj Trinidad, WI.
Re: Proper HTTP Support
Author: Remy Lebeau (TeamB)
Date: Thu, 03 Apr 2008 00:00
Date: Thu, 03 Apr 2008 00:00
42 lines
2393 bytes
2393 bytes
"Colin B Maharaj" <noreply@myhost.com> wrote in message news:47f3feb1$1@newsgroups.borland.com... > Note: I did not use the HTTP Server component that came with Indy9. Why not? > Then, in the last few months I have been able to add HTTP Deflate > using the ZLIB Library Indy 10 has native support for GZip and Deflate. > If I move to Indy10 and the HTTP Server lock, stock and barrel, > will I be getting SSL, Deflate and If-None-Match/304 support in > the server If-None-Match, no. The others, yes. > I saw a brief description of Indy10 support for 'A' as in WSA > Asynchronous support Indy 10 does not have any WSA asynchronous support in it. > claiming to be better supported for many thousands of connections. What you are referring to is separate add-on framework (the SuperCore package) that was never finished. It is very outdated now as it has not been worked on for a long time. > But I remember years ago I saw (heard) (cannot remember) that > Indy is based on blocking server technology for it implementation Yes. Indy has always used blocking sockets. > What's the story with this, should I go with indy10 new super core > structure or stick with the blocking model. Since SuperCore does not work, you have to stay with the blocking model. Gambit
Re: Proper HTTP Support
Author: Colin B Maharaj
Date: Thu, 03 Apr 2008 00:36
Date: Thu, 03 Apr 2008 00:36
64 lines
3078 bytes
3078 bytes
Thanks very much Remy for your patience (forbearance) in addressing these concerns. Your comments were very helpful. W.r.t Indy10, I really want to give it a go - just time, And I know that there will be a bit of a learning curve for 'me' and moving to a new platform like this is tricky for me right now. Frankly I need to hire a tester - Stability is important and also understanding any quirky behavior or implementation details that comes with the package. And frankly I will be rewriting my application for 'enterprise' class load and performance. When that time comes, Indy10 will surely be a must. Remy Lebeau (TeamB) wrote: > "Colin B Maharaj" <noreply@myhost.com> wrote in message > news:47f3feb1$1@newsgroups.borland.com... > >> Note: I did not use the HTTP Server component that came with Indy9. > > Why not? > >> Then, in the last few months I have been able to add HTTP Deflate >> using the ZLIB Library > > Indy 10 has native support for GZip and Deflate. > >> If I move to Indy10 and the HTTP Server lock, stock and barrel, >> will I be getting SSL, Deflate and If-None-Match/304 support in >> the server > > If-None-Match, no. The others, yes. > >> I saw a brief description of Indy10 support for 'A' as in WSA >> Asynchronous support > > Indy 10 does not have any WSA asynchronous support in it. > >> claiming to be better supported for many thousands of connections. > > What you are referring to is separate add-on framework (the SuperCore > package) that was never finished. It is very outdated now as it has not > been worked on for a long time. > >> But I remember years ago I saw (heard) (cannot remember) that >> Indy is based on blocking server technology for it implementation > > Yes. Indy has always used blocking sockets. > >> What's the story with this, should I go with indy10 new super core >> structure or stick with the blocking model. > > Since SuperCore does not work, you have to stay with the blocking model. > > > Gambit > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads