anvil.session.net

ClientSessionContainer and ServerSessioncontainer in anvil.session.net package implement simple client-server session system. There exists one central session server and zero or more client session server, connecting central server. Communication occurs in a simple line based protocol. Client side server never holds any information about session contents, all data are tranferred back-on-forth in serialized format on demand.

See also sessioncontainer.

Server side attributes
`name`	`default`	`description`
allow	`-`	Comma separated list of hostnames allowed to access this server container. If empty, no hosts are allowed to connect.
port	`9000`	Port to listen to.
maxthreads	`10`	Maximum number of threads active at same time.
maxtasks	`30`	Maximum number of tasks to serve at same time. If this number if higher than the maxthreads then some of requests will have to wait until threads became avilable.

Client side attributes
`name`	`default`	`description`
host	`localhost`	Hostname of server session container.
port	`9000`	Port of server session container.

Server example:

  sessioncontainer:
    provider   = anvil.session.net.ServerSessionContainer
    idlength   = 20
    allow      = njet.org, njet.net, njet.com
    port       = 9001
    maxthreads = 5
    maxclients = 10
  end

Client example:

  sessioncontainer:
    provider = anvil.session.net.ClientSessionContainer
    idlength = 20
    host     = njet.org
    port     = 9001
  end

See also | Providers

Anvil