Geh,
I see that 10038 could be caused because the server I am posting to does not
allow the connection to be created. I don't check for this. Could it be
the problem?
/Richard
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> skrev i meddelandet
news:44961289$1@newsgroups.borland.com...
>
>
> "Richard Bibby" <richard.bibby@profdoc.se> wrote in message
> news:4495a5c6@newsgroups.borland.com...
>
>> However occasionally I get a socket error when posting
>> the SMS message.
>
> What does the code look like? What is the exact error?
>
>> I assume that this is because the idHTTPServer component
>> has the socket open.
>
> That is not true. TIdHTTP will create its own socket instance on a
> different port than the one the TIdHTTPServer is using.
>
> > Could I have two sockets open if I used a different port?
>
> Yes. Sockets always use random ports by default for the exact purpose of
> being unique from other sockets. It is only when applications try to lock
> down the port values explicitally that conflicts can occur.
>
>> If not I guess its ok to gracefully handle the socket error, back
>> off a bit, and then retry?
>
> There is no way to answer that without knowing more about what is actually
> happening to begin with.
>
>
> Gambit
