home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hacker Chronicles 2
/
HACKER2.BIN
/
1091.WP.DOC
< prev
next >
Wrap
Text File
|
1989-03-29
|
4KB
|
144 lines
WP Cache Server Functions
The WP Cache server collects data releated to callsigns
and answers queries using that data.
The data is collected from WP messages transiting the MailBox,
from message headers, and from logged in users.
The data collected for each user is: Callsign, Home BBS,
Zip or Postal Code, Name, QTH.
The "I" group of commands are used to view the data,
the EU command is used to manually change it if required.
A WP query is a message addressed to WP. Each line of the message
is the callsign, a space, and a question mark. WP returns a line
containing all information about that callsign.
There are several parameters in CONFIG.MB to control the operation of WP:
1) The global WP Server callsign.
If this is blank, then you will act as Global WP Server.
2) The YES/NO tag that turns on Cache Server operation.
If this is NO, then no WP Server operation is enabled.
3) The YES/NO tag that turns on @ BBS checking for messages.
W0RLI White Pages Server - Technical and Operational Information.
WP Entry Types and their Lifetimes.
1. Sysop Locked Entries.
Flags: B - Allowed to connect on "BBS only" ports.
S - Permitted to be remote sysop.
X - Excluded.
Lifetime: TTLWS - Normally 0 (forever).
These entries are created when you add the B, S, or X flags to
an existing WP entry.
2. Local User Entries.
Flags: None. Home MailBox callsign same as this system callsign.
Lifetime: TTLWL - Normally 40 days.
This entry holds the information
3. Known BBS Entries.
Flags: I - Is a BBS.
Lifetime: TTLWL - Normally 40 days.
4. User of Other BBS Entries.
Flags: None. Home MailBox callsign different than this system callsign.
Lifetime: TTLWL - Normally 40 days.
5. Temporary Entries.
Flags: None
Lifetime: None, deleted at logout.
These entries are not normally seen. If a station connects on a
"BBS only" port, and is then excluded, there will be a temporary
entry left in the database. This entry will only be seen if a
RECOVER is done before the database item is re-used.
6. Refreshed entry.
Flags: None.
Lifetime: TTLWF - Normally 60 days.
A refreshed entry is one that has had it's data sent to the next
level of WP server. This is done with an automatically generated
message to WP at the callsign you specify in CONFIG.MB. When the
data about a callsign is sent to the next level of WP server, that
callsigns entry is marked as Refreshed. After TTLWF days elapse,
the data in an entry is considered "no longer fresh" at the next
level of WP. The next time this callsign logs into your MailBox,
his WP data will be again sent to the next level of WP server, and
the entry marked as Refreshed.
WP Entry Dates.
1. First Seen.
This is the date that your WP server first learned of the callsign.
2. Last Seen.
This is the date that your WP server last saw the callsign.
It may have seen the callsign as a login, in a message to or from WP,
or in a message header.
3. Login.
This is the date that callsign last logged into your MailBox.
If this station has never logged into your MailBox, their Login
date is set to 1/1/88 to flag that fact.
4. Last Refresh.
This is the date your MailBox last refreshed the data on this callsign
to the next level of WP. This date is not normally displayed.
Interaction Between Entry Dates and Lifetimes.