[Top][All Lists]

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

Re: [Demexp-dev] Which architecture and languages for next developments?

From: David MENTRE
Subject: Re: [Demexp-dev] Which architecture and languages for next developments?
Date: Wed, 28 Dec 2005 22:14:36 +0100
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux)


David MENTRE <address@hidden> writes:

> I have already made a web interface to demexp[1] using the WDialog
> framework[2], which is using the OCaml language. WDialog allows to write
> web interface, and other OCaml modules allow to interface with SQL
> databases. If I follow the same approach, I would have roughly the
> following architecture:
>  Web browser <--HTTP--> WDialog interface <--demexp RPC--> demexp server
>                                 ^                               ^
>                                 |                               |
>                                 v                               v
>                           SQL database                       XML file

No much answer since my last post. :( 

Anyway, I dug a little more on the database side of this architecture
and even asked on the caml-list[1].  It appears that there are several
opportunities to store persistent information from OCaml:

 - Dbi module to interface with real databases (MySQL, ...) or SQLite

 - Berkeley DB;

 - standard OCaml's Dbm module.

The RAS which hosts demexp server provides MySQL database, also as a MySQL server. So, depending on our need to
make structured queries, we might use either Dbi/SQL or either Berkeley
DB. I'll tend to avoid Dbm as it appears to be quite sensible to
failures (somebody told me that privately).

I don't know yet our need regarding structured queries: it might be
useful to have a typed database and make queries on tables' content.

Best wishes,


pub  1024D/A3AD7A2A 2004-10-03 David MENTRE <address@hidden>
 5996 CC46 4612 9CA4 3562  D7AC 6C67 9E96 A3AD 7A2A

reply via email to

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