🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.socket
Article #2412

Multiple serversockets in a single executable?

#2412
From: Arska
Date: Wed, 26 Apr 2006 08:01
13 lines
1507 bytes
Hello

Is it possible to use two TServerSocket component in a single application? I
am writing a simple demonstration system, where several clients reports
their status to the server (first client-server connection). The second
client-server connection is an application where a client sends a request to
the server, which sends some data back. My server application is a single
executable. I have used two TServerSocket components. The first works ok,
but the second refuses to connect. It gives an event "On connecting", but
don't establish connection. Suggestions how to solve this. I have tested the
system in a single computer and I use ports 8001 and 8002.

Ari
Technical Details
Message-ID: <444f28ce@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!news4.google.com!news2.volia.net!solnet.ch!solnet.ch!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,3bf6510caf6f0f0e,start
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: "Arska" <joku@eiolemassa.fi>
Newsgroups: borland.public.cppbuilder.internet.socket
Subject: Multiple serversockets in a single executable?
Date: Wed, 26 Apr 2006 11:01:17 +0300
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
NNTP-Posting-Host: 130.188.112.160
Message-ID: <444f28ce@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1146038478 130.188.112.160 (26 Apr 2006 01:01:18 -0700)
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!news4.google.com!news2.volia.net!solnet.ch!solnet.ch!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail