That's an interesting idea. I've often wanted to have a go at a lightweight
server for IDB. Before discussing that further though, I'd just like to
point out that there's the RmiJdbc driver available that already lets you
use IDB in client-server mode. See
The problem I've always had with writing a dedicated server for IDB was it's
sheer size. You're quite right - it's a very *easy* thing to do (very little
actual thinking involved), but wouldn't it take a lot of time and effort? If
all you wanted to do was send SQL up to be executed then the server would
indeed be very small. Granted, that 90% of the time that's probably all you
do want to do, but java.sql has hundreds, if not thousands, of methods that
would have to be implemented. Wouldn't that involve inventing a line
protocol to cope with all of these methods?
If you've got a really easy way to avoid all that work I'd be *really* keen
to hear more about it.
Peter Hearty firstname.lastname@example.org
Lutris Technologies (UK) http://www.lutris.com
----- Original Message -----
From: "Robert J Milewski" <email@example.com>
To: "Peter Hearty" <firstname.lastname@example.org>
Cc: "Mark Diekhans" <email@example.com>; "instantDB"
Sent: Monday, October 30, 2000 5:37 PM
Subject: Re: instantdb evaluation
> There is a solution which you guys could design and it would be quick.
> You design a quick server - all it does is pass SQL and Resultsets (for
> example) through a socket - 1 socket per client connection. Then, on Unix,
> whichever user the server is executed on will handle the permissions
> automatically. So the server uses the driver and the .prp file to make the
> jdbc connection and it waits on a port for a socket connection. So this
> "server" which is less than 200 lines of code creates a 3-tier(
> architecture?) making any operating system blackbox. You would not have
> change any of the other database code you have, it would be independant.
> An addon I suppose to your existing software.
> Wadda ya think ? Would you guys be willing to design something like this ?
> It should take less than a week.
> Please send comments - thanx =)
> Robert Milewski (716) 645-6164 x538
> Research Engineer
> Center of Excellence for Document Analysis and Recognition
> SUNY Buffalo
> On Mon, 30 Oct 2000, Peter Hearty wrote:
> > Robert
> > AFAIK (and if I'm wrong - would someone out there please chip in and
> > correct), there's no way to explicitly set UNIX style file permissions
> > Java. There are limited capabilities in the java.io.File class, but
> > are mostly interrogative.
> > I think that means that, if you intend to access a database from
> > accounts, it's either a matter of setting up a group with appropriate
> > permissions or manually setting file permissions once the database has
> > created.
> > Any UNIX Guru's care to comment?
> > Regards
> > Pete
> > --
> > Peter Hearty firstname.lastname@example.org
> > Lutris Technologies (UK) http://www.lutris.com
> > ----- Original Message -----
> > From: "Robert J Milewski" <email@example.com>
> > To: <firstname.lastname@example.org>
> > Sent: Thursday, October 26, 2000 7:11 PM
> > Subject: instantdb evaluation
> > >
> > > To whom this may concern,
> > > I am a lead design engineer evaluating java database engines for
> > > one of our projects. While evaluating the latest release of your
> > > system in Solaris, I noticed that when I create or modify a table, the
> > > permissions, user and group information from my umask is used on the
> > > for that table. This prevents other users from having read/write
> > > that table. If there is something I have missed, please notify me
> > > found your system easy to use, but I would not want to scrap it b/c of
> > > improper handling of Unix permissions. Hopefully I missed something.
> > > Thank you for your time. =)
> > >
> > >
> > > Robert Milewski (716) 645-6164 x538
> > > Research Engineer
> > > Center of Excellence for Document Analysis and Recognition
> > > SUNY Buffalo
> > >
> > > http://www.cse.buffalo.edu/~milewski
> > >
> > >
> > >
To unsubscribe from this mailing list, send email to email@example.com
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at firstname.lastname@example.org.