X is analagous to Amanda in that its a matter of defining the
important resource.
In X its the SCREEN, not the CPU cycles that are important.
In amanda its arguably the central control, work area and
tape drive. Anything the clients request is a secondary effect
to the server initiation the process on the client anyway.
It can be argued multiple ways - and I'm not trying to start a
(pointless) war, just hoping to shed some light on the "resources"
in question and the accepted terminology of this particular domain.
On Sun, Dec 04, 2005 at 12:51:33AM -0500, Jon LaBadie wrote:
> On Sat, Dec 03, 2005 at 10:36:36PM -0700, mindfuq AT verizon DOT net wrote:
> > I've been reading the documentation on amanda.org, and it seems the
> > authors have this terminology flipped. Servers always passively
> > *listen* for a connection, while clients are active initiators. In
> > the Amanda model, the centralized backup host is actually a *client*,
> > because it's the active "consumer" that initiates connections, whereas
> > all the nodes on the network that have data to backup are servers
> > listening for a client - and serving the data on request.
> >
> > I find it confusing to read the Amanda documentation, because it
> > appears the Amanda Core Team is calling the server a "client", and
> > vice versa.
>
> You are trying for absolutes and there are precious few.
>
> Another example of a "server" initiating the connection is
> the X server when it initiates the connection with X terminals
> or PC serving as X terminals using the XDMCP protocol.
>
> --
> Jon H. LaBadie jon AT jgcomp DOT com
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
---
Brian R Cuttler brian.cuttler AT wadsworth DOT org
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773
|