PING
From ADCPortal Wiki
| Inclusion date | 1.0, 2008-05-03 |
|---|---|
| Created by | Pietry |
| Contributers | Catalin |
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).[1]
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).
Contents |
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):
[separator="|"]
| Code | Type | Description |
|---|---|---|
| HH | string | Hub Host address (DNS or IP) |
| WS | url | Hub Website |
| NE | string | Hub Network |
| OW | string | Hub Owner name |
| UC | integer | Current User count |
| SS | integer | Total share size |
| SF | integer | Total files shared |
| MS | integer | Minimum share required to enter hub (bytes) |
| XS | integer | Maximum share for entering hub (bytes) |
| ML | integer | Minimum slots required to enter hub |
| XL | integer | Maximum slots for entering hub |
| MU | integer | Minimum hubs connected where clients can be users |
| MR | integer | Minimum hubs connected where client can be registered |
| MO | integer | Minimum hubs connected where client can be operators |
| XU | integer | Maximum hubs connected where clients can be users |
| XR | integer | Maximum hubs connected where client can be registered |
| XO | integer | Maximum hubs connected where client can be operators |
| MC | integer | Maximum possible clients (users) who can connect |
| UP | integer | Hub uptime (seconds) |
| NI | string | Hub name (from BASE) |
| DE | string | Hub description (from BASE) |
| VE | string | Hub software version (from BASE) |
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)
