Looky 1.0.7
SourceForge.net Logo  
main page
about us

back  print  site



consumerActually just a string representation of a user application with specify meaning to a looky client.

A looky client may ask for a resource of a pool p for a consumer c.

The looky server will check if a resource in this pool p was already assigned to this consumer c. If this was already done in the past, looky will return this resource item. If no resource was ever assigned to consumer c in pool p, looky will use seed method to get a resource for the consumer. If a resource is available, looky will return this resource.
distribute modeThe behaviour of a pool in a situation where all available resources are consumed but an new consumer has asked for another.
latency timeA property of a pool. Defines how long resources are hold for an inactive consumer.
looky clientA component of the looky system. Actually used as short form of a looky balancer client. Within current release (1.0.7) there is just one client implemented: the looky cgi client.
looky serverA component of the looky system. Actually used as short form of a looky balancer server.
pool The looky system organizes its resources in pools. Each pool has a name and a set of resources. Each pool has its own seed method and latency time.
redirect rulesA set of rules that are applied by a looky balancer client to create a redirection header for consumers initial HTTP request.
resource Actually just a string with specific meaning to a looky client. Each resource is managed by a pool. Resource have a unique name inside a pool but may share the same name in different pools. Each resource has a quantity (a 'have' value) to denote the number of resource items looky may distribute to different consumers. Resources may be coupled or shared in beetween pools.
seed methodA property of a pool. Defines how to distribute resource items in beetween consumers. The current implementation (1.0.7) provides 4 seed methods: serial, parallel, weighted and minimal

HTML by: WebByWeb V1.3
last update: 2003-05-18 11:23
contact:./o about us