From: Eugen <pi...@de...> - 2007-11-30 11:32:17
|
=== PING - Pinger extension This extension can be supported by both clients and hubs, and when present, if hub supports it, it must send additional information to the client ( otherwise normal base client) When the client supporting the PING command connects, the hub must send its normal INF along with the following added fields ( none mandatory, if not present, it means hub has no restrictions in that matter ): HH - Hub Host address ( DNS or IP ) WS - Hub Website OW - Hub Owner name UC - Current User count SS - Total share size SF - Total files shared MS - Minimum share required to enter hub ( bytes ) XS - Maximum share for entering hub ( bytes ) ML - Minimum slots required to enter hub XL - Maximum slots for entering hub MU - Minimum hubs connected where clients can be users MR - Minimum hubs connected where client can be registered MO - Minimum hubs connected where client can be operators XU - Maximum hubs connected where clients can be users XR - Maximum hubs connected where client can be registered XO - Maximum hubs connected where client can be operators MC - Maximum possible clients ( users ) who can connect Inherited fields from BASE: NI - Hub Name DE - Hub Topic VE- Hub software version HU - This information is about the hub The hub may decide to disconnect pinger after all information is sent, or continue to send the user list as for a normal user ( move to NORMAL state ). |
From: Jacek S. <arn...@gm...> - 2007-12-01 11:12:32
|
Technically, these could be added to the existing ADC INF so that clients can detect them when logging in...and then possibly have an additional flag in the client INF which says "I'm a pinger"... /J Eugen wrote: > === PING - Pinger extension > This extension can be supported by both clients and hubs, and when > present, if hub > supports it, it must send additional information to the client ( > otherwise normal > base client) > > When the client supporting the PING command connects, the hub must send its > normal INF along with the following added fields ( none mandatory, if > not present, > it means hub has no restrictions in that matter ): > > HH - Hub Host address ( DNS or IP ) > WS - Hub Website > OW - Hub Owner name > UC - Current User count > SS - Total share size > SF - Total files shared > MS - Minimum share required to enter hub ( bytes ) > XS - Maximum share for entering hub ( bytes ) > ML - Minimum slots required to enter hub > XL - Maximum slots for entering hub > MU - Minimum hubs connected where clients can be users > MR - Minimum hubs connected where client can be registered > MO - Minimum hubs connected where client can be operators > XU - Maximum hubs connected where clients can be users > XR - Maximum hubs connected where client can be registered > XO - Maximum hubs connected where client can be operators > MC - Maximum possible clients ( users ) who can connect > > Inherited fields from BASE: > NI - Hub Name > DE - Hub Topic > VE- Hub software version > HU - This information is about the hub > > > > > The hub may decide to disconnect pinger after all information is sent, > or continue > to send the user list as for a normal user ( move to NORMAL state ). > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > dcplusplus-devel mailing list > dcp...@li... > https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel > |
From: Eugen <pi...@de...> - 2007-12-01 11:18:40
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=windows-1252" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> If they're added to the existing INF, then all clients get the info which is useless bandwidth usage.<br> If the client has the PING value in the SU field, then the hub could add these extra fields to it's <br> INF command.<br> If so, it means that these fields are added to BASE ? or just client-based advertising ?<br> It's a feature that both hub and client can support, its not c-c related so my opinion is that <br> it's supposed to be advertised in the initial SUP string...<br> A minor correction : <br> removing "HU - This information is about the hub"<br> since its deprecated in latest ADC specs.<br> <br> <br> <br> Jacek Sieka wrote: <blockquote cite="mid:475...@gm..." type="cite"> <pre wrap="">Technically, these could be added to the existing ADC INF so that clients can detect them when logging in...and then possibly have an additional flag in the client INF which says "I'm a pinger"... /J Eugen wrote: </pre> <blockquote type="cite"> <pre wrap="">=== PING - Pinger extension This extension can be supported by both clients and hubs, and when present, if hub supports it, it must send additional information to the client ( otherwise normal base client) When the client supporting the PING command connects, the hub must send its normal INF along with the following added fields ( none mandatory, if not present, it means hub has no restrictions in that matter ): HH - Hub Host address ( DNS or IP ) WS - Hub Website OW - Hub Owner name UC - Current User count SS - Total share size SF - Total files shared MS - Minimum share required to enter hub ( bytes ) XS - Maximum share for entering hub ( bytes ) ML - Minimum slots required to enter hub XL - Maximum slots for entering hub MU - Minimum hubs connected where clients can be users MR - Minimum hubs connected where client can be registered MO - Minimum hubs connected where client can be operators XU - Maximum hubs connected where clients can be users XR - Maximum hubs connected where client can be registered XO - Maximum hubs connected where client can be operators MC - Maximum possible clients ( users ) who can connect Inherited fields from BASE: NI - Hub Name DE - Hub Topic VE- Hub software version HU - This information is about the hub The hub may decide to disconnect pinger after all information is sent, or continue to send the user list as for a normal user ( move to NORMAL state ). ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. <a class="moz-txt-link-freetext" href="http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4">http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4</a> _______________________________________________ dcplusplus-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:dcp...@li...">dcp...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel">https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel</a> </pre> </blockquote> <pre wrap=""><!----> ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. <a class="moz-txt-link-freetext" href="http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4">http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4</a> _______________________________________________ dcplusplus-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:dcp...@li...">dcp...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel">https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel</a> </pre> </blockquote> <br> </body> </html> |