Advice for creating a TCP server component

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

2 messages

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

2 total messages Started by Pere Mateu Sun, 02 May 2004 18:11

#5730

Author: Pere Mateu
Date: Sun, 02 May 2004 18:11

15 lines
1318 bytes

Hi,

I want to create a non-visual component that implements an application
protocol that works over TCP. There's basically two ways of doing this:

1) Deriving a component from TComponent with a TServerSocket as one of its
properties.

2) Deriving the component directly from TServerSocket and overriding its
methods.

Which way would you choose?

Thanks very much,
Pere.

Re: Advice for creating a TCP server component

#5731

Author: Remy Lebeau (TeamB)
Date: Sun, 02 May 2004 18:55

14 lines
1472 bytes

"Pere Mateu" <pmateu@ono.com> wrote in message
news:409539d1@newsgroups.borland.com...

> Which way would you choose?

That depends on how much direct access to the socket you want to provide to
the user.  If you want to let the user access the socket directly and do
manual operations on the socket, then derive from TServerSocket.  Otherwise,
wrap the TServerSocket inside another class that doesn't expose the
TServerSocket publically at all.


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