Idea: It would be handy to have an Events component about foundatio

[niemyjski]

@ejsmith: Could we do this with the new attached behaviors?

[ejsmith]

I think you would want to use the messagebus for this. You could publish a message from wherever you are saving the file and then you could subscribe to that event and enqueue an action to happen or just do the action right then. Does that make sense?

[chrispauly]

I was thinking leveraging the messagebus would make the most sense too... since it already has the pub/sub functionality and ability to perform an action based on an object type (which would be the specific EventArgs message for whatever event occurred). This architecture seems like a way you could provide metrics across every function (as long as they implement the event messaging).

Also, it's a way that I've used in the past to handle asynchronous processing of synchronous tasks cross-processes.

[niemyjski]

@chrispauly did you end up going with the message bus approach? After rereading all of this it seems like that is what you were wanting to use. Is this correct? If not please let us know. Also, please feel free to close this issue if you feel this use case is solved.

[chrispauly]

Oh, I never did anything with this. It was just an idea I had after you presented at the MadDotNet meeting last year. I really liked this collection and just thought that Eventing was something that I leverage in many apps I built and thought it would fit right into a foundational collection. I've changed jobs since last year and haven't written any new custom apps that could use these objects, but if I do find the need I will definitely look at forking and/or creating a pull request.