[FLOW3-general] Persisting resources

[Adrian Föder]

Hi Bastian, and list,

following your recommendation I got used to the TYPO.Media package, 
which offered me exactly what I needed: Image handling at all and an 
image repository. I will update my gist once finished, in case somebody 
other would need it.


Best and thanks,

Adrian

On 26.10.2011 17:51, Bastian Waidelich wrote:
> 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