You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bernt M. Johnsen (JIRA)" <ji...@apache.org> on 2007/05/15 10:29:16 UTC
[jira] Commented: (DERBY-2412) Refactor NetworkServerControlImpl
[ https://issues.apache.org/jira/browse/DERBY-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495891 ]
Bernt M. Johnsen commented on DERBY-2412:
-----------------------------------------
I will back out this one. I think a more iterative approach like the one Dan proposed will work better. I will start afresh after 10.3 is out. I'll see if https://issues.apache.org/jira/browse/DERBY-2363 may be implemented for 10.3 without this one.
> Refactor NetworkServerControlImpl
> ---------------------------------
>
> Key: DERBY-2412
> URL: https://issues.apache.org/jira/browse/DERBY-2412
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Reporter: Bernt M. Johnsen
> Assigned To: Bernt M. Johnsen
> Priority: Minor
> Attachments: derby-2412-v1.diff, derby-2412-v1.stat
>
>
> NetworkServerControlImpl is overly complex and serves several purposes. This makes it hard to penetrate the logic, to debug and to maintain.
> I propose (actually, I've alread done a whole lot) to tear it apart and move the current semantics into the following new classes:
> NetworkServer - the actual network server code
> NetworkAdminServer - the implementation of network administration commands (ping, shutdown etc)
> NetworkAdminClient - the client for network administration of Derby
> NetworkAdminProtocol - the administration command protocol (as opposed to the DRDA protocol)
> plus a couple of utility classes (common methods, common constants, error messaging, exceptions etc)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.