2009/12/22 Broken Pipe <[email protected]>

> "1-You can just the Id from the Browse Product presenter to the Edit
> Product." I guess you was going to write:
> You can just pass the Id from the Browse Product presenter to the Edit
> Product presenter. Well it doesn't matter what i pass, whole product
> or just ID, i can always reread it from current presenter|session. The
> problem is how to pass information between presenters, as i said i
> don't want to expose presenters to presenters.
>

So you are looking for:
Event/publisher, Prism has a nice Event publishing mechanism.
And the example of Ayende Rahien, effectus:
http://msdn.microsoft.com/en-us/magazine/ee819139.aspx has an artifact for
event-publishing.
If you are using CpBT, this is the CpBT version of Effectus:
http://jfromaniello.blogspot.com/2009/12/reviewing-and-changing-effectus.html
domain events: http://www.udidahan.com/2009/06/14/domain-events-salvation/


BTW in the former mail you said:

The Problem: I can't update entities passed from one presenter to another,
> as you may guess I'm getting "Illegal attempt to associate a collection with
> two open sessions" Exception.










>
> 2) I have studied your Chinook Media Manager, nice architecture but
> unfortunately it doesn't show how to solve my situation, basically as
> i understood you do all main work in one session "AlbumManagerModel"
> and u close it only on "save all" or "cancel all". When you load
> artist you close session after it and load almubs in new View using
> new session, track editing goes in same AlbumManagerModel session.
>
> I'm my case when i load my Products, 1) i need to stay List session
> open 2) I need to display Product details in same view (that all
> hapens in 1 prsenter|session)
> When i edit Prpoduct i do it in new view|presenter|session, and i have
> to reload this product passed from ListVIew in EditView session, when
> i save it i need to reload it in ListView etc etc.
>
> My actual model is pretty complex i have about 16 interconnected
> Entities with duplex associations, so far i have done only 3 entities
> and it's already produce lots of in-memory \ view sync problems and
> persistent problems, i will be unable to hold all this working with
> all my model implemented.
> So now i see only 3 options for me:
> 1) Load all my ObjectGraph in memory and work with it (not good it
> will consume about 700MB of memory)
> 2) Invent some kind of smart object like smart pointers in C++ which
> will auto manage session.
> 3) Think more )
>


Well, chinook architecture is gum architecture..............

--

You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.


Reply via email to