TcpClient & TcpServer in Turbo C++ (TurboExplorer)

Thread View: borland.public.cppbuilder.internet.socket

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Victrix Sat, 09 Dec 2006 18:44

#1625

Author: Victrix
Date: Sat, 09 Dec 2006 18:44

19 lines
1875 bytes

Hi all,

I'm using free Turbo C++ (turboexplorer) and this environment missing help 
files for TcpClient & TcpServer Components, someone know where to get 
information about this Components?, i try to use indy but is not included 
either.

I was using TClientSocket & TServerSocket (C++ Builder 5) sometime ago 
without problems, now, when i try to make a connection using non-blocking 
mode i got a 10035 (WSAEWOULDBLOCK) error and got connection with server, 
never got the OnConnect event and Active property is false :s, i never had 
this problem with TClientSocket, well, i know 10038 is a normal timing 
problem for non-blocking connections, but dont know how to fix it with this 
component. When i was tring to use blocking mode, dont know what method use 
for receive messages.

Well, thanks for your time and help.

Vic. :)

Re: TcpClient & TcpServer in Turbo C++ (TurboExplorer)

#1626

Author: Remy Lebeau (TeamB)
Date: Sun, 10 Dec 2006 05:55

32 lines
1961 bytes

"Victrix" <vrivero00NoSpamATNoSpam.yahoo.com.mx.invalid> wrote in message
news:457b03c5$1@newsgroups.borland.com...

> I'm using free Turbo C++ (turboexplorer) and this environment missing
> help files for TcpClient & TcpServer Components, someone know where
> to get information about this Components?

Those are very poorly designed components.  I strongly advise not using
them.

> I was using TClientSocket & TServerSocket (C++ Builder 5) sometime
> ago without problems

You can still use them.

> now, when i try to make a connection using non-blocking mode i got
> a 10035 (WSAEWOULDBLOCK) error

That is a perfectly normal error code with non-blocking sockets.  It is not
a fatal error.  It simply means that you tried to do something that would
block the calling thread for any length of time, which obviously is not
allowed with a non-blocking socket.

> never got the OnConnect event and Active property is false :s, i never had
> this problem with TClientSocket

TClientSocket and TServerSocket handle that specific error code internally
for you.


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