You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/01/21 10:48:35 UTC
[jira] Created: (SLING-178) Jobs should not need a job id
Jobs should not need a job id
-----------------------------
Key: SLING-178
URL: https://issues.apache.org/jira/browse/SLING-178
Project: Sling
Issue Type: Improvement
Components: Event
Reporter: Carsten Ziegeler
Currently a job needs a unique job id in order to update a job. In many cases jobs don't need the id.
Removing the need for an id could speed up the implementation as well as no locking of the repo is required in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-178) Jobs should not need a job id
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-178.
----------------------------------
> Jobs should not need a job id
> -----------------------------
>
> Key: SLING-178
> URL: https://issues.apache.org/jira/browse/SLING-178
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> Currently a job needs a unique job id in order to update a job. In many cases jobs don't need the id.
> Removing the need for an id could speed up the implementation as well as no locking of the repo is required in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-178) Jobs should not need a job id
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-178.
------------------------------------
Resolution: Fixed
> Jobs should not need a job id
> -----------------------------
>
> Key: SLING-178
> URL: https://issues.apache.org/jira/browse/SLING-178
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> Currently a job needs a unique job id in order to update a job. In many cases jobs don't need the id.
> Removing the need for an id could speed up the implementation as well as no locking of the repo is required in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-178) Jobs should not need a job id
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-178:
-----------------------------------
Assignee: Carsten Ziegeler
> Jobs should not need a job id
> -----------------------------
>
> Key: SLING-178
> URL: https://issues.apache.org/jira/browse/SLING-178
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> Currently a job needs a unique job id in order to update a job. In many cases jobs don't need the id.
> Removing the need for an id could speed up the implementation as well as no locking of the repo is required in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.