You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Stanley Bradbury <St...@gmail.com> on 2006/05/09 02:51:19 UTC
[WWD] Check of edits from : Review of Final Chapters (5 and 6)
John Embretsen wrote:
> === SNIP ====
> <quote 1 from "Activity notes", p.6 (8)>
> A client program is often created to allow database access and updates
> from multiple computers on the network.
> </quote>
>
> I don't think this statement is correct. It is not the "client
> program" that allows access from multiple computers, it is the server
> framework that does this. Would you like to rephrase?
>
>
> <quote 2 from "Activity notes", p.6 (8)>
> Derby's two architectures have caused confusion for some new Derby
> users. They mistakenly think that embedded is a single user
> configuration. Not true. The embedded driver supports multiple
> simultaneous connections, performs locking and provides performance,
> integrity and recoverability.
> </quote>
==== SNIP ====
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. ...
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.
Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
This is my bad -- the web site is linking to workingwithderby.pdf
instead of to WorkingWithDerby.pdf. --I didn't catch the name change on
the web site.
fixing ....
-jean
Stanley Bradbury wrote:
> Daniel John Debrunner wrote:
>
>> The various versions of WWD at
>>
>> http://db.apache.org/derby/manuals/index.html#latest
>>
>> are out of date. The PDF version only has the first activity.
>>
>> Dan.
>>
>>
>>
>>
> Hi Dan -
>
> Thanks, I'll look into the PDF build problem - it should contain the
> first four chapters which have been committed. The HTML docs contains
> all four chapters so am hoping it is something simple with the PDF
> transform process. In the meantime you can use the verification copy of
> the PDF for Chapters 1-4 that is attached to Derby-913 - the download
> URL is:
>
> http://issues.apache.org/jira/secure/attachment/12325929/CheckCommitWWD-Ch1-4.pdf
>
>
> The final two chapters are near the end of the review period. I intend
> to submit the patch to be committed tomorrow barring new major issues.
> The initial draft without the changes from the review can be viewed by
> downloading:
>
> http://issues.apache.org/jira/secure/attachment/12326037/ReviewPDF_wwdCh5and6rv1.0.zip
>
>
> The changes are fairly minor - One: renaming the 'miscellanea' section
> and changing the links as described in my message to Jean:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200605.mbox/%3c44569B46.3010005@gmail.com%3e
>
>
> Two: And rewritten two of the Activity notes as shown in:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200605.mbox/%3c445FE787.5070509@gmail.com%3e
>
>
>
>
Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Posted by Stanley Bradbury <St...@gmail.com>.
Daniel John Debrunner wrote:
>The various versions of WWD at
>
>http://db.apache.org/derby/manuals/index.html#latest
>
>are out of date. The PDF version only has the first activity.
>
>Dan.
>
>
>
>
Hi Dan -
Thanks, I'll look into the PDF build problem - it should contain the
first four chapters which have been committed. The HTML docs contains
all four chapters so am hoping it is something simple with the PDF
transform process. In the meantime you can use the verification copy of
the PDF for Chapters 1-4 that is attached to Derby-913 - the download
URL is:
http://issues.apache.org/jira/secure/attachment/12325929/CheckCommitWWD-Ch1-4.pdf
The final two chapters are near the end of the review period. I intend
to submit the patch to be committed tomorrow barring new major issues.
The initial draft without the changes from the review can be viewed by
downloading:
http://issues.apache.org/jira/secure/attachment/12326037/ReviewPDF_wwdCh5and6rv1.0.zip
The changes are fairly minor -
One: renaming the 'miscellanea' section and changing the links as
described in my message to Jean:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200605.mbox/%3c44569B46.3010005@gmail.com%3e
Two: And rewritten two of the Activity notes as shown in:
http://mail-archives.apache.org/mod_mbox/db-derby-user/200605.mbox/%3c445FE787.5070509@gmail.com%3e
Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Daniel John Debrunner wrote:
> The various versions of WWD at
>
> http://db.apache.org/derby/manuals/index.html#latest
>
> are out of date. The PDF version only has the first activity.
thanks for the catch. The html versions have everything that has been
committed to date, but there must be a problem with the pdf build.
-jean
Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Posted by Daniel John Debrunner <dj...@apache.org>.
The various versions of WWD at
http://db.apache.org/derby/manuals/index.html#latest
are out of date. The PDF version only has the first activity.
Dan.
Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Posted by Stanley Bradbury <St...@gmail.com>.
John, as always, your suggestions are helpful, thank you. I will use
your improved wording in quote 2.
[EOM]
John Embretsen wrote:
> 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?
>
>
Re: [WWD] Check of edits from : Review of Final Chapters (5 and 6)
Posted by John Embretsen <Jo...@Sun.COM>.
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