db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3064) Implement the LogShipper that will enable the shipping of Log records from the master to the slave
Date Mon, 24 Sep 2007 11:51:50 GMT

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

Jørgen Løland commented on DERBY-3064:
--------------------------------------

> Does this mean atleast in the case of log shipper we would be forced to use threading
since the DaemonService interval cannot be varied?

In the general case, we should use DaemonService whenever possible to keep uniformity with
existing Derby code. As far as I have seen, no Derby class implements Runnable... 

In this case, however, a separate "homemade" thread may be better since you'll have to use
an eternal loop. The API of  DaemonService/Factory says that the performWork method should
not take much time. Eternal loops hardly fit that description ;) 

Unless someone has a strong argument for not creating a thread (as opposed to using Derby's
DaemonService), I think you should go for a normal Java thread in this particular case.

> Implement the LogShipper that will enable the shipping of Log records from the master
to the slave
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3064
>                 URL: https://issues.apache.org/jira/browse/DERBY-3064
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: LogShipperImpl_v1.diff, LogShipperImpl_v1.stat
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message