PING

From ADC Project

PING - Pinger extension

Status: Added as of 14 Mar 2008 to specification.

Actual implementation since 23rd Jan 2008 in DSHub

Actual implementation since 8th Feb 2008 in Hubtracker.com

Pinger - Hub communication

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).

It's purpose is to send to hublist pingers additional information about the hub that otherwise it would be impossible to get as a normal user (eg. minimum share, maximum user count, etc).

INF

Contexts : F

When the client supporting the PING extension 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, or non existent):

HH - Hub Host address ( DNS or IP )

WS - Hub Website

NE - Hub Network

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

UP - Hub uptime, a number in seconds


Inherited fields from BASE:

NI - Hub Name

DE - Hub Topic

VE- Hub software version


The hub must continue to send the user list as for a normal user ( move to NORMAL state ). The pinger may decide to go through or disconnect ( eg. if it doesn't require additional information about the users ).

Example :

-pinger- HSUP ADBASE ADPING AD..
-hub- ISUP ADBASE ADPING AD..
-hub- ISID ..
-hub- IINF NIhubname DEcurrent\stopic VE.. HHmyhub.no-ip.org:555 WShttp://myhub.no-ip.org/ OWmyname UC2231 SS.. SF.. MS0 ML0 MC5000
- (pinger may disconnect)
-..

Hub - Hublist communication

The same extension goes for hub- hublist communication. This way, the hub takes the role of the client and the hublist of the server.

The hublist may send INF about itself with NI field which would become hublist name and WS hublist web address.

Example :

-hub- HSUP ADBASE ADPING AD..
-hublist- ISUP ADBASE ADPING AD..
-hublist- IINF NIhublist_name WShublist_address
-hub- HINF  NIhubname DEcurrent\stopic VE.. HHmyhub.no-ip.org:555 WShttp://myhub.no-ip.org/ OWmyname UC2231 SS.. SF.. MS0 ML0 MC5000
-( disconnect )