You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iota.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/30 00:37:58 UTC
[jira] [Commented] (IOTA-34) Add Global Watch Service to Fey
[ https://issues.apache.org/jira/browse/IOTA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707059#comment-15707059 ]
ASF GitHub Bot commented on IOTA-34:
------------------------------------
GitHub user barbaragomes opened a pull request:
https://github.com/apache/incubator-iota/pull/27
[IOTA-34] - Global Watch Service
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/barbaragomes/incubator-iota IOTA-34
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-iota/pull/27.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #27
----
commit 3d2e99d9a8e989a4a10910f19169b3d8cf1345c8
Author: Barbara Gomes <ba...@gmail.com>
Date: 2016-11-04T19:58:35Z
[IOTA-34] Add Global Watch Service to Fey
- No tests added yet
commit 5a528b50a1ae693157e2bc55ba64b81e07abf63b
Author: Barbara Gomes <ba...@gmail.com>
Date: 2016-11-14T18:53:50Z
Adding comment on config
commit 4775f9905bb0382e515978da31adac107ec7035a
Author: Barbara Gomes <ba...@gmail.com>
Date: 2016-11-30T00:35:36Z
Merge branch 'master' of github.com:apache/incubator-iota into IOTA-34
# Conflicts:
# fey-core/src/main/scala/org/apache/iota/fey/FeyCore.scala
----
> Add Global Watch Service to Fey
> -------------------------------
>
> Key: IOTA-34
> URL: https://issues.apache.org/jira/browse/IOTA-34
> Project: Iota
> Issue Type: Task
> Reporter: Barbara Gomes
> Assignee: Barbara Gomes
> Priority: Minor
>
> Some performer implementation requires watch a file directory for file events like CREATE, UPDATE and DELETE.
> If each performer implements its own Watch Service, it means that each one will have an additional thread for watching the directory which would be a waste of resources in most cases, since Fey could have one only thread that watches all necessary directories for all running performers and send a message to the performer once it receives the event that the performer is looking for.
> *Suggestion:*
> Fey will implement its own *Global Watch Service* and will be responsible for keeping it running and distribute the events to the right Performers.
> In order to use it, the performer will have to send a message to the Global Watch Service Actor on Fey that contains:
> * ActorRef
> * Directory Path
> * Optional File name (In case it is watching for changes on a specific file)
> * List of Watch Events that it is waiting for
> The FeyGenericActor will offer a new method that would be called every time the Performer receives a new event. It would contain:
> * Path
> * Event type
> {code}
> This approach will require changes on FeyGenericActor.
> All performers will have to be updated.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)