🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

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

Re: detect router

#4140
From: Hans Galema
Date: Tue, 22 Mar 2005 23:46
43 lines
3049 bytes
Remy Lebeau (TeamB) wrote:

> While the machine is off, it cannot retreive files, and it cannot provide
> files to other users. 

;-)

> The connection to the central server should be
> persistent so that the server can detect when the machine goes away.  That
> way, it can stop returning that machine in searches that other clients
> perform.

If the server would guarantee that a client was up then I agree.

>>I wanted to deny your statement that a permanent
>>connection was needed.
>
> I never said that a permanent connection *to the ISP* was needed. 

No that was indeed to a centralized server.

 > I said
> that a persistent connection *to the centralized server that is maintaining
> the searchable database* was needed.  

I don't remember those words as such.

 > Those are very different things.  You
> keep discussing the former.  Jonathan was asking about the latter instead.

The term persistent was not used until this post. And Jonathan used
the word permanent. So therefore my mixing up with permanent connection
to the internet and a permanent connection to a server which is indeed
persistent then.

May be I caused confusion with my replies. Sorry. I do understand
that while operating a persistent connection is used. But then I wanted
to say that closing the program and switching the computer off would
do no harm. There would be another day.

And my thoughts were to much with Napster I think.

Hans.
Technical Details
Message-ID: <4240aeea$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail
References: <423a7852$1@newsgroups.borland.com> <423a95b5$1@newsgroups.borland.com> <423aa0ca$1@newsgroups.borland.com> <423ab09b@newsgroups.borland.com> <423ac0ff@newsgroups.borland.com> <423ada46$1@newsgroups.borland.com> <423b0983@newsgroups.borland.com> <423b1ceb$1@newsgroups.borland.com> <423b3d0f$1@newsgroups.borland.com> <423b4b3b$1@newsgroups.borland.com> <423f632d@newsgroups.borland.com> <423f6e1a$3@newsgroups.borland.com> <423f7f77$1@newsgroups.borland.com> <423fc134$1@newsgroups.borland.com> <423fc8c6@newsgroups.borland.com> <42407e08$2@newsgroups.borland.com> <4240929d$1@newsgroups.borland.com> <424096d0@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,a79eaa4c33b47254
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
Date: Wed, 23 Mar 2005 00:46:56 +0100
From: Hans Galema <notused@notused.nl>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: borland.public.cppbuilder.internet.socket
Subject: Re: detect router
References: <423a7852$1@newsgroups.borland.com> <423a95b5$1@newsgroups.borland.com> <423aa0ca$1@newsgroups.borland.com> <423ab09b@newsgroups.borland.com> <423ac0ff@newsgroups.borland.com> <423ada46$1@newsgroups.borland.com> <423b0983@newsgroups.borland.com> <423b1ceb$1@newsgroups.borland.com> <423b3d0f$1@newsgroups.borland.com> <423b4b3b$1@newsgroups.borland.com> <423f632d@newsgroups.borland.com> <423f6e1a$3@newsgroups.borland.com> <423f7f77$1@newsgroups.borland.com> <423fc134$1@newsgroups.borland.com> <423fc8c6@newsgroups.borland.com> <42407e08$2@newsgroups.borland.com> <4240929d$1@newsgroups.borland.com> <424096d0@newsgroups.borland.com>
In-Reply-To: <424096d0@newsgroups.borland.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 129.125.201.248
Message-ID: <4240aeea$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1111535338 129.125.201.248 (22 Mar 2005 15:48:58 -0800)
Lines: 45
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail