gawk vs sql

Date: Sat, 7 Aug 1999 20:09:33 -0700 (PDT)
From: Ian White <iwhite@victoria.tc.ca>
To: John Nemeth <jnemeth@victoria.tc.ca>
cc: Jeff Warnica <jwarnica@ns.sympatico.ca>, Michael Smith <michael@csuite.ns.ca>, CCN Tech <ccn-tech@chebucto.ns.ca>, csuite-dev@chebucto.ns.ca
Precedence: bulk
Return-Path: <csuite-dev-mml-owner@chebucto.ns.ca>

next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects

Index of Subjects
On Sat, 7 Aug 1999, John Nemeth wrote:

> On Aug 5, 11:00am, Jeff  Warnica wrote:
> 
>      I think it will be several years yet before Community Nets can
> move completely away from standard text logins.  At this time it is
> easy for the financially disadvantaged to get older computers (ranging
> up to 386's and low-end 486's), since these are basically give-away
> items.  However, these machines are not suitable for running current
> Internet apps.  For that, you need a high-end 486 (486DX4/100 w/16M RAM
> and 500M HD minimum), or more preferable, a Pentium class machine.
[snip]
>      I would like to get comments from other CSuite users/sites on the
> above.

This is one of the major things that has come up from VTN users since the
announcement of upcoming PPP. Many users with lowend machines fear that
they are going to lose their connection because their machine can't handle
PPP. Although there are many users saying "Oh boy graphics!" theres just
as many saying "Please don't do anything to leave us behind".

> } Official or not I think most of the prople working on the new suff for the
> } provincial server (Csuite v2) realise that sql is the way to go, if just
> } because most of the stuff will be run from inside a phpN script. We /could/
> } have every php script call out to other programs, but we would have to
> } rewrite everything, anyway.
> 
>      So far I have not seen a good reason for moving away from namedb
> to a more complex SQL implementation.  The limitations of a particular
> scripting language (in this case, PHP) simply do not count.  If a
> language can not handle your needs, then use another.

One posibility could be LDAP, which would allow CSuite to hold all of the
UNIX login stuff for each user and use that as a password file (assuming
OS support exists for it), but also hold all of the namedb stuff and
anything else that comes up in the future (like using it as the RADIUS
database). It seems more designed to act as the "address book" that namedb
needs than SQL, but still gives you the possibility of moving it onto a
seperate machine, etc.

Of course, you still need to modularize everything and make an interface
for both namedb and the password file access.

Ian

-------------------------------------------
Ian White
BC Community Networks Association (BCCNA)
email: iwhite@victoria.tc.ca
phone: 250-727-2489


next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects