Xavier,
yes we're off topic here. Partitioning means when to register what and
what gets registered with what. It feels from what you're describing you
need to just register stuff in such a way you can avoid having
duplicates when you don't need them.
On 11/03/2011 6:32 PM, Xavier wrote:
I agree: nothing to do with lifestyle/lifetime. But, what's the
difference between partitioning and scoping ? If i could create a
'client scope' and a 'server scope', it would solve my problem. Am i
off topic ?
On 11 mar, 00:30, Krzysztof Koźmic<[email protected]> wrote:
Xavier,
this feels to me more like a registration partitioning problem than a
lifestyle/lifetime problem.
Krzysztof
On 11/03/2011 12:21 AM, Xavier wrote:
The main problem is related to components that are registered by the
server + the client: when we mix both assemblages, we get two
components for the same service. In most cases, only one component is
resolved but it shares client and server context which is not
expected.
On 9 mar, 11:15, Krzysztof Koźmic<[email protected]> wrote:
Thanks for the feedback Xavier,
Can you share some more details on the second scenario? What friction
points have you encountered specifically?
Krzysztof
On 09/03/2011 8:05 PM, Xavier wrote:
Really interesting and useful.
We have a MDI application and we have decided to use child container
to solve this scope problem. But it's not perfect.
Another scenario: our application is client/server but we wanted to
have a standalone version (for demo, debug, etc.). To get it, we have
wired the client container (and child containers) with the server
container, bypassing the communication layer (no more proxies). We've
had a lot of problems because of 'scoping': some client components
were in conflict with server's ones. Finally, we have not reused the
client-server wiring and used a specific one for this scenario.
Xavier
On 9 mar, 03:15, Krzysztof Koźmic<[email protected]> wrote:
Yeah,
that's one of the main scenarios I want this to support. I'm scribbling
some ideas right now... I'll post that once it solidified a bit...
On 09/03/2011 11:53 AM, hammett wrote:
Interesting. Is there a variation that will allow a component to
start/end a scope in runtime?
Suppose you have a MDI app. Each File | New Document is potentially
starting a new 'document' scope.
2011/3/8 Krzysztof Koźmic<[email protected]
<mailto:[email protected]>>
Hi,
I created a site in the wiki where I'll throw my semi-structured
thoughts and ideas for implementing one of the biggest new
features for Windsor Wawel (aka vNext) - scoping.
http://docs.castleproject.org/Windsor.Scratchpad-scopes-in-Windsor-co...
<http://docs.castleproject.org/Windsor.Scratchpad-scopes-in-Windsor-co...>
I would really appreciate if you guys shared your thoughts and
ideas on this (it's an open wiki - go wild, contribute to the
brainstorming).
Also make sure you click the small semi-hidden envelope icon in
upper right corner to subscribe to notifications of changes to the
site.
Thanks in advance for all your ideas and contributions. If we get
this done, we should be pretty much ready to release first preview.
cheers,
Krzysztof
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
Cheers,
hammett
http://hammett.castleproject.org/
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" 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/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" 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/castle-project-devel?hl=en.
