🚀 go-pugleaf

"Hans Galema" <notused@notused.nl> wrote in message 
news:438d7645$1@newsgroups.borland.com...
> Lee wrote:
>
> To make a webserver you need to create a TCP/IP server that listens 
> on -default-
> port 80 and understands the HTTP protocol. You did not tell what kind
> of things your application does now that could be used for the webserver 
> too.
> Nor did you tell why you think you need Apache API for creating a 
> webserver. Well
> I do not know Apache API so please explain.
* My application acts like a normal webserver but parses the incoming http 
POST for certain command strings which it passes to other parts of my 
distributed app. I don't think I NEED Apache API to create a webserver, but 
I want ot know if the API can be used to simplify the process - look at it 
like this:  I can do 3D animation on the pc natively, but using the DirectX 
API makes it much easier.

> How did you implement http ? Did you think of using TIdHTTP ? Don't know 
> if
> it supports https though.
*  Can't use that - I need it to be cross platform so I can't use the VCL. 
I also don't want to use CLX as it's not supported anymore.

> You can create a webserver using just sockets instead of a component. You 
> have
> to implement the http protocol yourself then. What you have in mind with 
> 'using
> the Apache API' I don't know.
~ Yup, but it's much harder work, especially if you are using SSL too.

> If you mean: using code from the Apache project. Yes you can do that if 
> you
> follow the rules.
* True, but again I was trying to avoid that - because of how Apache works 
then extracting code will probably be just as much work as starting again.

As an aside, after further research, I think the Apache API isn't what I 
expected it to be - I think it's used purely for Apache module creation - 
can anyone confirm this?

> Hans.
Thanks,   Lee.