See my comments below.
On Fri, 2005-11-04 at 15:24, vishal saberwal wrote:
> thanks for your response,
>
> We are kind of jailing (may be hiding would be a better term)
> resources behind the database/Stored procedures and GUI needs to have
> a feel as if the data is comming from database.
> Its a requirement for the project that any communication of resources
> and data be done through stored procedures/function calls.
> What other options do you suggest.
Hmm... this sounds like an application server is what you need. The app
server is the interface to the user, and should get the data from the
file system or data base or whatever else. Now some data base vendors
would argue that you can do all what you need with the DB and put all
code into it, but I guess that's just not true (there are more efficient
ways to store some data than a data base, and a web server will
definitely serve you files faster than any DB), and an efficient setup
will need a separate application server in front of the data base. For
one thing, it is a lot easier to cluster/scale the app server than the
data base, and you can use it to integrate multiple data sources. IMHO,
using the data base as an app server is just a bad choice.
> Did try finding something about HFS for ext3/xfs but in vain. The
> information i found was the conversion between these file systems.
>
> There are not just the Users but different devices and applications as
> clients that would talk to the database and may not require the web
> servers.
If you're coding your clients, then you can code them to access any
given API, including HTTP, or even some proprietary API/protocol you
design. HTTP is not made only for humans, and I guess is as easy to
write code which accesses data through HTTP as it would writing code
accessing any of the postgres client APIs. Or maybe it's not that easy,
but not a lot harder.
[snip]
HTH,
Csaba.
