| scheduling rules in synchronization jobs [message #57669] |
Thu, 11 September 2008 17:47  |
Eclipse User |
|
|
|
hello mylyn community,
i am in the process of creating a mylyn connector for our commercial change
management system. the SDK provided by that system requires each access to
one specific server instance to be queued. the already existing eclipse
feature for that system uses job scheduling rules to that means. those rules
use the server instance as mutex. since different task repositories in our
connector may target the same server, using those scheduling rules for all
jobs is paramount to avoid deadlocks. mylyn synchronize jobs use their own
flavor of a rule in which the task repository becomes the mutex.
my question is now: could the ISynchronizationSession be extended or other
entry points be provided in for instance
org.eclipse.mylyn.tasks.core.AbstractRepositoryConnector#pre Synchronization(org.eclipse.mylyn.tasks.core.sync.ISynchroni zationSession,
org.eclipse.core.runtime.IProgressMonitor) to override/extend the rule to be
used by the synchronization job(s). basically all jobs needed to be
scheduled by rule in our environment ... query, task ...
many thanks for your feedback in advance,
klaus
|
|
|
|
| Re: scheduling rules in synchronization jobs [message #58205 is a reply to message #57804] |
Mon, 22 September 2008 17:30  |
| Eclipse User |
|
|
|
thank you, steffen!
i just filed bug # 248199
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=248199) and hope it is what
you had in mind. the scheduling rule extension would really help me avoiding
deadlocks in the command-queue of our SDK or peppering my code with
synchronize-blocks.
all the best,
k
"Steffen Pingel" <steffen.pingel@tasktop.com> wrote in message
news:gape2d$tj8$1@build.eclipse.org...
> Hi Klaus,
>
> your use-case have not come up before. I would suggest to file an
> enhancement request in the Mylyn Bugzilla:
>
> http://www.eclipse.org/mylyn/bugs/
>
> Generally development related questions are best directed at the mylyn-dev
> or mylyn-integrators mailing list:
>
> http://www.eclipse.org/mylyn/community/
>
> Steffen
>
>
> Klaus Wenger wrote:
>
>> hello mylyn community,
>>
>> i am in the process of creating a mylyn connector for our commercial
>> change management system. the SDK provided by that system requires each
>> access to one specific server instance to be queued. the already existing
>> eclipse feature for that system uses job scheduling rules to that means.
>> those rules use the server instance as mutex. since different task
>> repositories in our connector may target the same server, using those
>> scheduling rules for all jobs is paramount to avoid deadlocks. mylyn
>> synchronize jobs use their own flavor of a rule in which the task
>> repository becomes the mutex.
>>
>> my question is now: could the ISynchronizationSession be extended or
>> other
>> entry points be provided in for instance
>>
> org.eclipse.mylyn.tasks.core.AbstractRepositoryConnector#pre Synchronization(org.eclipse.mylyn.tasks.core.sync.ISynchroni zationSession,
>> org.eclipse.core.runtime.IProgressMonitor) to override/extend the rule to
>> be used by the synchronization job(s). basically all jobs needed to be
>> scheduled by rule in our environment ... query, task ...
>>
>> many thanks for your feedback in advance,
>>
>> klaus
>
|
|
|
| Re: scheduling rules in synchronization jobs [message #593258 is a reply to message #57669] |
Tue, 16 September 2008 19:04 |
| Eclipse User |
|
|
|
Hi Klaus,
your use-case have not come up before. I would suggest to file an
enhancement request in the Mylyn Bugzilla:
http://www.eclipse.org/mylyn/bugs/
Generally development related questions are best directed at the mylyn-dev
or mylyn-integrators mailing list:
http://www.eclipse.org/mylyn/community/
Steffen
Klaus Wenger wrote:
> hello mylyn community,
>
> i am in the process of creating a mylyn connector for our commercial
> change management system. the SDK provided by that system requires each
> access to one specific server instance to be queued. the already existing
> eclipse feature for that system uses job scheduling rules to that means.
> those rules use the server instance as mutex. since different task
> repositories in our connector may target the same server, using those
> scheduling rules for all jobs is paramount to avoid deadlocks. mylyn
> synchronize jobs use their own flavor of a rule in which the task
> repository becomes the mutex.
>
> my question is now: could the ISynchronizationSession be extended or other
> entry points be provided in for instance
>
org.eclipse.mylyn.tasks.core.AbstractRepositoryConnector#pre Synchronization(org.eclipse.mylyn.tasks.core.sync.ISynchroni zationSession,
> org.eclipse.core.runtime.IProgressMonitor) to override/extend the rule to
> be used by the synchronization job(s). basically all jobs needed to be
> scheduled by rule in our environment ... query, task ...
>
> many thanks for your feedback in advance,
>
> klaus
|
|
|
| Re: scheduling rules in synchronization jobs [message #593394 is a reply to message #57804] |
Mon, 22 September 2008 17:30 |
| Eclipse User |
|
|
|
thank you, steffen!
i just filed bug # 248199
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=248199) and hope it is what
you had in mind. the scheduling rule extension would really help me avoiding
deadlocks in the command-queue of our SDK or peppering my code with
synchronize-blocks.
all the best,
k
"Steffen Pingel" <steffen.pingel@tasktop.com> wrote in message
news:gape2d$tj8$1@build.eclipse.org...
> Hi Klaus,
>
> your use-case have not come up before. I would suggest to file an
> enhancement request in the Mylyn Bugzilla:
>
> http://www.eclipse.org/mylyn/bugs/
>
> Generally development related questions are best directed at the mylyn-dev
> or mylyn-integrators mailing list:
>
> http://www.eclipse.org/mylyn/community/
>
> Steffen
>
>
> Klaus Wenger wrote:
>
>> hello mylyn community,
>>
>> i am in the process of creating a mylyn connector for our commercial
>> change management system. the SDK provided by that system requires each
>> access to one specific server instance to be queued. the already existing
>> eclipse feature for that system uses job scheduling rules to that means.
>> those rules use the server instance as mutex. since different task
>> repositories in our connector may target the same server, using those
>> scheduling rules for all jobs is paramount to avoid deadlocks. mylyn
>> synchronize jobs use their own flavor of a rule in which the task
>> repository becomes the mutex.
>>
>> my question is now: could the ISynchronizationSession be extended or
>> other
>> entry points be provided in for instance
>>
> org.eclipse.mylyn.tasks.core.AbstractRepositoryConnector#pre Synchronization(org.eclipse.mylyn.tasks.core.sync.ISynchroni zationSession,
>> org.eclipse.core.runtime.IProgressMonitor) to override/extend the rule to
>> be used by the synchronization job(s). basically all jobs needed to be
>> scheduled by rule in our environment ... query, task ...
>>
>> many thanks for your feedback in advance,
>>
>> klaus
>
|
|
|
Powered by
FUDForum. Page generated in 0.03825 seconds
Home