OpenEuphoria

Re: DB - Final Question

• Posted by Ray Smith <smithr at ix.net.au> Feb 09, 2001
• 433 views

Hi,

I haven't followed this thread but if Web development is required
I think you should seriously look at zope (www.zope.org).
It has a built in Web Server/DB Server and a framework for web
development.
Extra modules can be written using Python or download from the
dozens already created.

It's GPL'd and can also connect to pretty much any other web server/DB
server you could think of.

I'm not saying it's the answer but it should definitely be considered.

Ray Smith


----- Original Message -----
From: Irv Mullins <irvm at ellijay.com>
To: EUforum <EUforum at topica.com>
Sent: Saturday, February 10, 2001 1:23 PM
Subject: Re: DB - Final Question


> On Fri, 09 Feb 2001, CK wrote:
>
> > For my current project, I need a database (Eu or MySQL), front-end (Eu
or
> > ?), and web server (Eu or ?). Right now I'm focusing on the database and
> > front-end. Here are my options:
> >
> > 1. Eu database with Eu front-end
> > 2. MySQL database with Eu front-end
> > 3. MySQL database with xx front-end
> >
> > Concerns:
> >     a. multi-threads - for multi-user access
> >     b. web serving
> >     c. scalability - for millions of records in multiple databases
> >     d. multi-platform capability - starting w/Linux but client might
want a
> > Windows version in future
> > Anybody else, please provide your comments! I'm making a final decision
and
> > starting work on this project Sunday (Feb. 11, 2001).
>
> CK:
>
> When you say "web serving"  - do you mean the db will be converted to html
> and served over the web in read/only mode?  - or does it need to be
accessable
> as a real, multi-user app with remote client programs reading/writing and
> updating the db?
>
> If it's a two way app then you'll need file and record locking. Euphoria
> can't do that.
>
> Nor would an Eu server be appropriate. Apache should be able to handle the
> load.  Euphoria cgi's might suffice for managing the communications
between the
> web  clients and your database. MySQL would probably be a good start, but
if
> the job is as big as you describe, you'll eventually need to look at
Oracle.
>
> Regards,
> Irv
>
>