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 2010/10/08 16:47:31 UTC

[jira] Created: (SLING-1830) Improve write acesses for job execution

Improve write acesses for job execution
---------------------------------------

                 Key: SLING-1830
                 URL: https://issues.apache.org/jira/browse/SLING-1830
             Project: Sling
          Issue Type: Improvement
          Components: Extensions
    Affects Versions: Extensions Event 2.4.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Extensions Event 3.0.0


Currently, the flow for a job is:
- write the job to the repository
- lock the node
- add the PROCESSOR info
- remove the node or unlock it and set some props

We can at least skip the PROCESSOR info and set it at the end.

In addition we should base the job handling completly on observation

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

[jira] Resolved: (SLING-1830) Improve write acesses for job execution

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1830.
-------------------------------------

    Resolution: Fixed

The job handling is now based on observation - it uses some shortcuts for improved performance.
In addition the processor information is only written for jobs with a job id to skip one roundtrip per execution to the repository.

> Improve write acesses for job execution
> ---------------------------------------
>
>                 Key: SLING-1830
>                 URL: https://issues.apache.org/jira/browse/SLING-1830
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Extensions Event 2.4.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Event 3.0.0
>
>
> Currently, the flow for a job is:
> - write the job to the repository
> - lock the node
> - add the PROCESSOR info
> - remove the node or unlock it and set some props
> We can at least skip the PROCESSOR info and set it at the end.
> In addition we should base the job handling completly on observation

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