Comments on QuickList please

Nev · Post by **Nev** » 2003-01-06 06:52

I would like to have some thoughts on QuickList so that we can agree on 1.0 and start implementing it!

http://forum.dcstats.net/showthread.php?s=&threadid=802

sandos · Post by **sandos** » 2003-01-06 14:28

Looks nice. If a client never wants updates about other users (search bots, hublist bot), does it have to use the normal DC way of connecting then?

aDe · Post by **aDe** » 2003-01-15 13:33

this is a good topic.. quicklist must be implemented soon.. however there is one problem that i can see.. the regular nmdc hub could not be scripted to support this!

TasMan · Post by **TasMan** » 2003-01-15 16:35

In my hub/client software that I'm making, I've put in QuickList support (though since I've started a new project, I'm doing a complete rewrite)....it's a good system for both the client and the hub

TasMan · Post by **TasMan** » 2003-01-16 18:55

Got only one problem though - but that is more a product of my own lazyness than anything

Obviously if the hub supports QuickList I'm ok but then again, if it doesn't, I have to put in some sort of timer/etc to make sure I send $ValidateNick. Some hubs have EXTENDEDPROTOCOL in their Lock but don't have $Supports/QuickList, so I can't rely on that

.

Unless....somebody has a better idea on how to approach it?

(Though maybe some comments on this - screw the "Lock" routine - use it as $Supports - ex $Lock SUPPORTSPROTOCOL QuickList etc| - save a little bit....if it sends $Key before $Supports it will be considered non QuickList, etc)

TasMan · Post by **TasMan** » 2003-01-16 18:56

I didn't make sense in the last part of the post.

Though maybe some comments on this - screw the "Lock" routine - use it as $Supports - ex $Lock SUPPORTSPROTOCOL QuickList etc| - save a little bit of bandwidth....if the client sends $Key before $Supports it will be considered non QuickList, etc user

That's better

TasMan · Post by **TasMan** » 2003-01-16 19:05

Another one of my quadruple posts again

I don't think (might be wrong) that a space or dollar sign are valid inside a Lock. We can always use - or * etc.

ender · Post by **ender** » 2003-01-17 04:16

TasMan · Post by **TasMan** » 2003-01-17 05:38

Oops.

Nev · Post by **Nev** » 2003-01-18 05:02

I recognize the flaw. Could we please take this is ash-forum, so we can keep it together? I'm hoping that we could tie up all loose ends, and get busy coding....

Post by **arnetheduck** » 2003-01-27 10:18

TasMan wrote:Got only one problem though - but that is more a product of my own lazyness than anything :)

Obviously if the hub supports QuickList I'm ok but then again, if it doesn't, I have to put in some sort of timer/etc to make sure I send $ValidateNick. Some hubs have EXTENDEDPROTOCOL in their Lock but don't have $Supports/QuickList, so I can't rely on that :( .

Unless....somebody has a better idea on how to approach it?

(Though maybe some comments on this - screw the "Lock" routine - use it as $Supports - ex $Lock SUPPORTSPROTOCOL QuickList etc| - save a little bit....if it sends $Key before $Supports it will be considered non QuickList, etc)

Oh, this is very easy, if a hub sends extendedprotocol it also has to reply with supports after it gets one...even if it doesnt support anything...as to the other hubs that dont work, who cares? They'll fix their flaws if they want to play with the rest of the children...

TasMan · Post by **TasMan** » 2003-01-27 10:38

They'll fix their flaws if they want to play with the rest of the children...

Well if you put it that way....

I suppose there aren't enough hubs that do this to worry about anyways....I hope.