InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors


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

Re: InstantDB: Synchronized Servlets


Okay -- I guess my question is devolving down to
whether the servlet engine is using multiple
JVM's.  I'm not using Enhydra -- I'm writing
servlets to run at an ISP (mycgiserver.com) which
is running jserv under apache.  But I believe
there is only one JVM.   I can check on that.

Thanks for the help.

Steve

----- Original Message -----
From: "Thom Nelson" <thom@lutris.com>
To: <instantDB@enhydra.org>
Sent: Wednesday, March 21, 2001 11:43 AM
Subject: Re: InstantDB: Synchronized Servlets


| The only time you'd want to use the RmiJdbc
driver is when accessing the
| same InstantDB database using two or more Java
Virtual Machine
| processes.  You should have no problem accessing
the same database from
| within the same JVM.  If you're running two
servlets in one instance of
| Enhydra, for example, you won't run into any
issues using the same
| InstantDB database.
|
| Thom
|
| Steve Carton wrote:
| >
| > Thom,
| >
| > I guess I'm a little surprised by that.  I
would
| > have thought if I created a synchronized,
static
| > method encapsulating my IDB action, since
statics
| > are shared by all servlet instances, it would
| > prevent a collision.
| >
| > Steve
| > ----- Original Message -----
| > From: "Thom Nelson" <thom@lutris.com>
| > To: <instantDB@enhydra.org>
| > Sent: Tuesday, March 20, 2001 5:34 PM
| > Subject: Re: InstantDB: Synchronized Servlets
| >
| > | Hi Steve,
| > |
| > | This will not work, because you will still
have
| > different instances of
| > | instantdb running against the same database
| > files.  This will inevitably
| > | result in corrupted data, since much of
| > instantdb's state is cached in
| > | memory.  This isn't a threading issue;
instantdb
| > works fine with
| > | multiple threads, just not multiple VMs.
| > |
| > | Thom
| > |
| > | Steve Carton wrote:
| > | >
| > | > I'm wondering if I can achieve the same
effect
| > as the RmiJdbc server from a
| > | > servlet if I encapsulate the JDBC code in
| > synchronized methods?
| > | >
| > | > Anyone try that?
| > | >
| > | > Steve Carton
| ------------------------------------------------
-----------------------------
| To unsubscribe from this mailing list, send
email to majordomo@enhydra.org
| 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 owner-instantdb@enhydra.org.

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
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 owner-instantdb@enhydra.org.