Re: Request for comments on deciding between implementing embedded or client-server -

[Stanley Bradbury <St...@gmail.com>]

Thanks again John.  The point Halley raises is a good one. [EOM]

John Embretsen wrote:

> Stanley,
>
> since you are working on a new embedded vs client/server/embedded 
> server document, you may be interested in the discussion surrounding 
> DERBY-1293, "Derby Server and Administration Guide - 
> derby.drda.startNetworkServer" at
> http://issues.apache.org/jira/browse/DERBY-1293
>
>
> Stanley Bradbury wrote:
>
>> Starting New thread from the following :
>>
>
> [SNIP]
>
>>>> It is arguable that the topic does not belong in an introductory  
>>>> document at all because it deals with system architecture as well  
>>>> as the specific meaning of terms like 'single-user', 'client- 
>>>> server', 'networking' and 'interprocess communication'.  Clearing  
>>>> up the confusion is out of the scope of this document.  Your  
>>>> suggestion, however,  has me thinking I should draft a short paper  
>>>> on the topic that can be referred to when questions like yours are  
>>>> raised and will begin working on this.  Do you think this will 
>>>> help  with the issue you raise?  I hesitate to include the 
>>>> standard  caution about access from multiple-JVMs as I perceive 
>>>> this as  contributing to the mind-set that using the embedded 
>>>> driver is  limiting.
>>>> I would really like to hear your thoughts on this and maybe begin 
>>>> a  new thread on the topic of when to use Network Server and when 
>>>> the  embedded driver is sufficient.  It seems there is enough in 
>>>> this  topic for a lively discussion.
>>>
>
> [SNIP]
>
>> Hi Craig -
>> You are correct. There is what has been termed the 'embedded server' 
>> architecture as well but this is well out of the scope of a 
>> introductory document like WWD.
>> However, since I hope to spin-off a thread discussing the various 
>> implementation architectures then 'embedded server' should be include.  
>
>
> [SNIP]
>
>