db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Embretsen <John.Embret...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-1194) Derby Server and Administration Guide - Managing the Derby Network Server
Date Fri, 21 Apr 2006 11:43:10 GMT
Dag H. Wanvik wrote:

> "John H. Embretsen (JIRA)" <derby-dev@db.apache.org> writes:
>> [ 
>> http://issues.apache.org/jira/browse/DERBY-1194?page=comments#action_12374701
>>  ]
>> John H. Embretsen commented on DERBY-1194: 
>> ------------------------------------------
>> Here is another suggestion which captures both interpretations of the 
>> sentence "The Derby Network Server can run as a stand-alone server, with
>>  Derby as an embedded part of the application.":
>> "The Derby Network Server can either run stand-alone, that is as an 
>> independent Java process embedding the Derby database engine, or 
>> embedded within another Java application. In the latter ("embedded 
>> server") setting both the Network Server framework and Derby are loaded 
>> by the Java application."
> I like this wording better than those suggested so far in this thread, 
> although I'd put "setting" in front of the parenthesized clause.

I agree, that would be better.

> However, this still fails to capture explicitly the fact that the 
> embedding application can access Derby using the embedded driver while 
> also offering access to other applications via the client driver and the 
> server.

Yes, but I am not sure how much of this should be included on the particular
manual page in question, with the title "Managing the Derby Network Server".

That said, the only place I could find something like this mentioned in the
manuals is in the admin guide, under "Network Server sample programs for
embedded and client connections",


Perhaps the best solution would be to include a link to this page from the
"Managing the Derby Network Server" page, i.e. something like this:

"An application embedding the Network Server can access Derby using both the
embedded driver and a client driver. For more information and examples, see

It is likely that the embedded server scenario is not documented well enough
in the manuals. But I guess that is something for another day, in another
Jira issue.


View raw message