Support non-entity event raising

[charlessolar]

In certain circumstances it would be useful to allow posting events not apart of an entity.

Take the example:

You have an "EmployeeType" field, which presents the user with a list of already stored employee types or allows them to add another. Making this type of object an entity or aggregate doesn't make sense as it only has one field "Name" with 1 or 2 commands (create, destroy).

Instead of that we can make a

_uow.Raise<Events.EmployeeType>("STREAM", x => {
x.Name= Name;
});

feature to support directly posting an event to a named stream.

The event consumers would see the event and store the employee type name in a table which would be given to the user next time he searches for an employee type.
No need for a domain object at all - because there is no business logic for these objects

[charlessolar]

For slightly more complicated objects that still do not have business logic but can be used IN business logic - EX: Something like a "CanSelect" property to mark the EmployeeType as selectable

It would be better to allow them to read and write POCOs to a stream.

_uow.For<EmployTypePoco>("STREAM", x => { 
x.Name = Name;
x.Selectable = true;
});

For reading/writing we would simply read/append to the last "event" on the stream. Kind of similar to a snapshot.