[FLOW3-general] Persisting resources

[Bastian Waidelich]

Adrian Föder wrote:

Hi Adrian,

> https://gist.github.com/1313125

> [...] Two things are missing: an entry in the ...resource_resource table
> (i.e. the persistence of the Resource object) and an idea how I could send
> information back, like the image itself and identity information.

As far as I can see it from your example, you never add the resource to 
an aggregate root, so it's never correctly persisted.

> Consider the composing progress of a web-based email: You have an
> (anonymous, not-yet-identitie'd) Email open where you can type To:, CC:,
> text, and add attachments. The attachments have to be uploaded parallely.

In that case you would probably have an Email object, that has a 
collection of Attachments attached (hihi) which again contains the resource.
You could leave out the Attachment model and link Resources directly of 
course, but an Attachment could have some additional properties/behavior.


HTH
Bastian