[jira] Created: (CONNECTORS-152) Notification implementation is clunky because it does not change the state of jobs entering notification

2011-01-23 Thread Karl Wright (JIRA)
Notification implementation is clunky because it does not change the state of 
jobs entering notification


 Key: CONNECTORS-152
 URL: https://issues.apache.org/jira/browse/CONNECTORS-152
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Framework crawler agent
Reporter: Karl Wright
Priority: Minor


The notification phase of crawling is gated by the Job Notification Thread, 
which does not actually change the state of the jobs undergoing notification.  
This is a potential future problem because there may someday be more than one 
thread doing it.


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



[jira] Assigned: (CONNECTORS-152) Notification implementation is clunky because it does not change the state of jobs entering notification

2011-01-23 Thread Karl Wright (JIRA)

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-152:
--

Assignee: Karl Wright

> Notification implementation is clunky because it does not change the state of 
> jobs entering notification
> 
>
> Key: CONNECTORS-152
> URL: https://issues.apache.org/jira/browse/CONNECTORS-152
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Framework crawler agent
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Minor
>
> The notification phase of crawling is gated by the Job Notification Thread, 
> which does not actually change the state of the jobs undergoing notification. 
>  This is a potential future problem because there may someday be more than 
> one thread doing it.

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



[jira] Resolved: (CONNECTORS-152) Notification implementation is clunky because it does not change the state of jobs entering notification

2011-01-23 Thread Karl Wright (JIRA)

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-152.


   Resolution: Fixed
Fix Version/s: ManifoldCF next

r1062556.


> Notification implementation is clunky because it does not change the state of 
> jobs entering notification
> 
>
> Key: CONNECTORS-152
> URL: https://issues.apache.org/jira/browse/CONNECTORS-152
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Framework crawler agent
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Minor
> Fix For: ManifoldCF next
>
>
> The notification phase of crawling is gated by the Job Notification Thread, 
> which does not actually change the state of the jobs undergoing notification. 
>  This is a potential future problem because there may someday be more than 
> one thread doing it.

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



[jira] Commented: (CONNECTORS-152) Notification implementation is clunky because it does not change the state of jobs entering notification

2011-01-23 Thread Karl Wright (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985443#action_12985443
 ] 

Karl Wright commented on CONNECTORS-152:


Also, r1062557.


> Notification implementation is clunky because it does not change the state of 
> jobs entering notification
> 
>
> Key: CONNECTORS-152
> URL: https://issues.apache.org/jira/browse/CONNECTORS-152
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Framework crawler agent
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Minor
> Fix For: ManifoldCF next
>
>
> The notification phase of crawling is gated by the Job Notification Thread, 
> which does not actually change the state of the jobs undergoing notification. 
>  This is a potential future problem because there may someday be more than 
> one thread doing it.

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