🚀 go-pugleaf

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.