hej,
I do not set BoundIP or BoundPort properties and when I get to work tomorrow
I will send you a copy of the code.
Why do you not recommend TTimer? Would it be better to start a thread and
use Sleep? The only problem then is I have to handle terminate requests in
my thread.
I'll find out which version I am using....
/Richard
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> skrev i meddelandet
news:4496e507$1@newsgroups.borland.com...
>
> "Richard Bibby" <richard.bibby@profdoc.se> wrote in message
> news:4496b9f4$1@newsgroups.borland.com...
>
>> Cound not bind socket Address and port are already in use.
>
> That should not be happening, unless you are setting the BoundIP and/or
> BoundPort properties on the TIdHTTP.
>
> Also, you did not say which specific version and build of Indy you are
> using
> in the first place.
>
>> Socket error # 10038. Socket operation on non-socket.
>> Socket error # 10022. Invalid argument.
>
> You did not show the code yet. Please do so.
>
>> If I understand you correctly there is no problem having a
>> tidHTTPServer component running in a service application
>> that also has a timer event that can trigger a call to idHTTP
>> to do a Post.
>
> I do not recommend using timers (TTimer in particular) inside of services.
> But yes, TIdHTTPServer and TIdHTTP can coexist in a service (or any other
> project type, for that matter).
>
>
> Gambit
