bug-gne
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnupedia] Architecture Questions


From: Tom Chance
Subject: Re: [Bug-gnupedia] Architecture Questions
Date: Sat, 20 Jan 2001 16:35:18 -0800 (PST)

On this note, it would be good to get some sort of
prototypes done for each system.
Now I'm a real Perl newbie, and Rob is just reading
mySQL stuff. We just know its advantages and general
workings, not its minutae setup and code, as yet lol.
So if anyone here knows sufficient Perl, DBI and CGI
stuff... come forward and maybe we could work on
getting a more detailed proposal for mine and Rob's
crackpot scheme!

Tom Chance

 
--- Rob Scott <address@hidden> wrote: > Yes the
document was written in a rush with bits
> added
> and bit taken away every now and then and its all
> higgledy piggledy and it probably dowsn't get the
> point across very well.
> 
> This is actually what I would like to do (make a
> prototype), but i did this coz we werent going to
> bother if you were all going to fly off on some xml
> thing.
> Its very straightforward approach because it is a
> result of a 3 hour conversation me and Thom had
> about
> it beforehand, so it doesnt seem to question many
> things.   I think our solution turns out to be a
> sort
> of slashdot/sourceforge approach. 
> 
> 
> --- Bryce Harrington <address@hidden> wrote: > On
> Sat, 20 Jan 2001, [iso-8859-1] Tom Chance wrote:
> > > Because any description of the servers needed
> some
> > > illustration, we (Rob Scott and I) put it up on
> a
> > web
> > > page found here:
> > > http://www.state-embers.co.uk
> > > Hector has looked and it and says its good, we
> > think
> > > so too. What about everyone else?
> > 
> > It needs a lot of work.  It's rather top level,
> and
> > mixes architectural,
> > implementational, and policy concepts together,
> > without backing them up
> > with rationale as to WHY.  Perhaps try breaking
> your
> > points down into a
> > bulletized fashion, and organizing them into
> > "requirements/policies" and
> > "architecture", and leave the implementational
> > details (like use of
> > MySQL, Perl, etc.) for later...
> > 
> > An alternative approach I might suggest is to just
> > go ahead and code up
> > a functional prototype of your ideas, that can be
> > played with.  Working
> > code is worth reams of documentation, and is
> usually
> > more fun to make.  ;-)
> > 
> > Bryce
> > 
> > 
> > _______________________________________________
> > Bug-gnupedia mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/bug-gnupedia
> 
> 
>
____________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.co.uk address at
> http://mail.yahoo.co.uk
> or your free @yahoo.ie address at
> http://mail.yahoo.ie
> 
> _______________________________________________
> Bug-gnupedia mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-gnupedia


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices. 
http://auctions.yahoo.com/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]