[ 
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010671#comment-17010671
 ] 

sagar commented on DERBY-6809:
------------------------------

This should be possibly my last post here ...

 

Just out of the blue a thought came to mind ...

 

Derby has 3 modes of operation embedded, hybrid and networkserver.

 

A question is why cant we operate Derby as a networkserver only ... and have a 
parameter in derby.properties files as mode ... SingleUser and MultiUser for 
Embedded and NetworkServer.

When singleuser/embedded is chosen ... the NetworkServer will boot and run only 
on localhost:1527 and enable only one active connection at a time. Derby will 
ignore the host and port property in this case and also have a tight default 
java security policy in place and also run with a tight default securitymanager.

For NetworkServer mode you can leave all the settings to the user.

This way a lot of code specifically for Embeded mode and Hybrid mode can be 
left out and possibly NetworkServer and NetworkClientJDBCDriver can be more 
optimized and focussed upon.

Just a wild thought.

 

 

 

> Java 1.8 feature use
> --------------------
>
>                 Key: DERBY-6809
>                 URL: https://issues.apache.org/jira/browse/DERBY-6809
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server
>    Affects Versions: 11.0.0.0
>            Reporter: sagar
>            Priority: Major
>         Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, 
> latest.png, nb8.png
>
>
> Suggestion ...
> Is it possible to auto modify the existing source code using tools like 
> Netbeans, and take advantage of the new features in JDK 1.8 for better 
> multiuser performance and better utilization of current day multicore 
> processors?
> Plainly put, can we have from 11.0 onwards a version of derby which takes 
> advantage of the advancements and new features in java 1.8 ... 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to