db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Embretsen <John.Embret...@Sun.COM>
Subject Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Date Tue, 09 May 2006 11:08:12 GMT
Stanley Bradbury wrote:

> John and other derby-users -
> 
> I have rewritten the two the paragraphs mentioned above to address the 
> points made by John.  Please let me know what you think.
> quote 1 from "Activity notes", p.6 (8)  REWRITE:
> In a client / server environment the client program is often used from 
> other computers on the network. ...

Sounds good, although it probably does not say everything you originally 
intended to say here.

> quote 2 from "Activity notes", p.6 (8) REWRITE:
> Derby's two architectures have caused confusion for some new Derby 
> users. They mistakenly think that embedded is a single user 
> configuration. This is not true. The embedded driver supports multiple 
> simultaneous connections, performs locking and provides performance, 
> integrity and recoverability. Any embedded application can open multiple 
> Derby connections and then provide a means for multiple users to 
> interact with the database on each connection. The Derby Network Server 
> is an example of such an application.

Very good! Though I think the term "any embedded application" can be 
ambiguous. Is "any application using the embedded driver" better?


-- 
John



Mime
View raw message