Hi, I have a question.
How can one keep an idle connection after "download complete" if there was no download. I know that sounds weird, but here is an example;
I'm working on QuickDC and click "Browse user" on a DC++ user.
I request a connection, log in properly and send;
$Get MyList.bz2$xxxx|
I get:
$FileLength yyyy|
Hm, that file is complete, then, now what?
I cannot "$Get" another file, unless $Send was called.
It's no point in $Send'ing unless you don't have that file.
DC++ doesn not support the $Canceled command either...
How should this be done?
Keeping idle conncetions
Moderator: Moderators
Keeping idle conncetions
I wrote QuickDC - A DC++ compatible client for Linux and FreeBSD.
-
- The Creator Himself
- Posts: 296
- Joined: 2003-01-02 17:15
OK, but what about other files in general?arnetheduck wrote:It can't (currently). I didn't consider this to be very important considering that bz lists seldom become larger than a few 100 k's...
If a file is n bytes long should I:
SEND: $Get file$n+1|
RECV: $FileLength n|
SEND: $Send| (nothing happens)
and the connection is idle?
I wrote QuickDC - A DC++ compatible client for Linux and FreeBSD.
-
- The Creator Himself
- Posts: 296
- Joined: 2003-01-02 17:15
That worked with DC++. I'll test it with the others aswell (dctc gives some really weird results most of the times...)
I wrote QuickDC - A DC++ compatible client for Linux and FreeBSD.