Subj : services
To   : MCMLXXIX
From : Digital Man
Date : Thu Oct 08 2009 05:54 pm

  Re: services
  By: MCMLXXIX to Digital Man on Thu Oct 08 2009 10:55 am

 > I'm working on this gaming service, and I'm a bit confused about a few
 > things.
 > Assuming my BBS is acting as the HUB, how can the service access other
 > connections to send data between two NODES?
 >
 > For example:
 >
 > Digital man runs chess.js on Vertrauen, it connects to the HUB via the
 > gaming service...
 >
 > Deuce runs chess.js on Synchronix, it also connects..
 >
 > Now I've got two clients connected to the HUB, who need to be able to
 > communicate with each other.
 >
 > Are service client connections stored in an array somewhere?
 >
 > I think I'm missing something obvious.

There are 2 types of Synchronet services:

Dynamic (or normal) Services:
These services are the simplest to write and the Synchronet Services module
does most of the work for you (opening the socket, binding the port, accepting
incoming connections). For each incoming connection, there is a separate
instance of the JavaScript (or native executable) to handle the client.
Multiple concurrent clients means multiple concurrent instances of the service.
fingerservice.js, gopherservice.js, nntpservice.js are examples of dynamic
services.

Static Services:
These services are executed when the Synchronet Services module starts up and
stay running through-out the life of the services module (or they may be
executed stand-alone via JSexec). Static services are responsible for accepting
their own connections and only one instance of the service script (or
executable) exists to handle all simultaneous client connections.
ircd.js and staticservice.js are examples of static services.

                                            digital man

Snapple "Real Fact" #5:
Camels have 3 eyelids.

.