[
https://issues.apache.org/jira/browse/PLUTO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated PLUTO-267:
---------------------------------
Attachment: eventing.fire_event_proposal.070607.patch
Here's a small proposal/patch how to simplify the event firing. I maybe missing
something, but to me carrying index and event name extracted already from the
event itself is a more complex than just passing the event itself to the
EventContainer.fireEvent method. This would also make the event providers
requirement to serve a ordered collection of events to the event request
obsolete. This removes the need of handling certain concurrency issues if
providing of registered events could be removed completely from driver api.
> Implementation of the new Eventing Model
> ----------------------------------------
>
> Key: PLUTO-267
> URL: https://issues.apache.org/jira/browse/PLUTO-267
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY
>
> Attachments: eventing.021106.patch,
> eventing.fire_event_proposal.070607.patch,
> eventing.moreeventsbug.051106.patch, eventing_rev14.240507.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
