db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: Embedded and Network Simultaneous Connections
Date Thu, 06 Nov 2008 15:29:59 GMT
Ole Ersoy wrote:
> Hi Michael,
> Thanks for the clarification.  That answers my question.

Hello Ole,

Please note that you can have your application use the embedded driver, 
and also start the the network server so that remote clients can connect 
to the same Derby instance.
I don't remember the details (please look at the documentation or wait 
for an answer), but I think you can set a property or start it though a 
Java API.

One scenario for this setup, is having your main application use Derby 
embedded and then connect remotely for "ad-hoc" access/maintenance or 
connection secondary clients.
Of course, opening up for remote connections has security implications. 
A white paper on security with Derby has been published on the Sun 
Developer Network site.

> Thanks again,
> - Ole
> derby@segel.com wrote:
>>> -----Original Message-----
>>> From: Ole Ersoy [mailto:ole.ersoy@gmail.com]
>>> Sent: Thursday, November 06, 2008 8:29 AM
>>> To: derby-user@db.apache.org
>>> Subject: Embedded and Network Simultaneous Connections
>>> Hi,
>>> I was wondering if it's possible for a network client to connect to a
>>> derby instance running in embedded mode.  So in other words client A is
>>> running embedded derby, and (client B - Separate JVM) wants to 
>>> connect to
>>> it using the network driver.
>>> Thanks,
>>> - Ole
>> I don't think your question make sense.
>> If you're running Derby in embedded mode, then you don't have a 
>> "client",
>> you have an application which has a derby database embedded in it.
>> So I think your question becomes "Application A has derby embedded in 
>> it. A
>> separate application B, on a different JVM, would like to connect to the
>> Derby instance running in A."
>> Since you specified that the instance of Derby is embedded there is no
>> network service started and thus you can't connect to that instance 
>> of Derby
>> unless you write your own service as part of application A.

View raw message