From: mela...@t-data.com
To: michaelwr...@yahoo.co.uk; opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
Hi,
I'm against a CommsManager class, on the grounds I'm against most
other *Manager classes.
They serve as holders for stuff that seems straightforward
initially
a usage point of view to what we have now.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 4:33 AM
Hi,
I'm against
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 9:44 AM
Well I agree the name CommsManager is a bad choice and I'm all for
changing/getting rid of that. I don't see this as a Manager but just another
registery of modules. My proposal
,
Stefan Andersson
Tribal Media AB
From: a...@deepthink.com.au
To: opensim-dev@lists.berlios.de; michaelwr...@yahoo.co.uk
Date: Thu, 26 Feb 2009 05:21:48 -0500
Subject: Re: [Opensim-dev] Comms Manager
Do we need the comms manager?
Can’t we just register them individually via
a...@deepthink.com.au wrote:
From: Frisby, Adam a...@deepthink.com.au
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 10:29 AM
Maybe this is worth using as an excuse to build that “middle-module”
we’ve
modules. but it would stop the sharing of modules between grid
and standalone mode.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 10:40 AM
What Adam
the
current shared Region modules. but it would stop the sharing of modules
between grid and standalone mode.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26
+1, looks good.
Best regards,
Stefan Andersson
Tribal Media AB
Date: Thu, 26 Feb 2009 11:38:52 +
From: mela...@t-data.com
To: michaelwr...@yahoo.co.uk; opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
Well, I wanted to remove that extra step in the global
: mela...@t-data.com
To: opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
You just can't let go of the centralistic *Manager idea..!
IMHO, clients have no business at app level. Clients connect to
regions through client stacks. Which can be shared modules
...@lists.berlios.de] On Behalf Of Stefan Andersson
Sent: Thursday, 26 February 2009 3:00 AM
To: opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
... did we not just come full circle?
I believe were all in agreement here, just varying on what to call stuff and
exactly what stuff
be a ApplicationPlugin, that
itself loaded IGridServiceModules. But the loader could also just as easily be
directly in core.]
--- On Thu, 26/2/09, Stefan Andersson ste...@tribalmedia.se wrote:
From: Stefan Andersson ste...@tribalmedia.se
Subject: RE: [Opensim-dev] Comms Manager
To: opensim-dev
To: opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
... did we not just come full circle?
I believe were all in agreement here, just varying on what to call stuff
and exactly what stuff they should be connected to.
I'm confident all that will sort itself
();
OnSceneRemoved();
}
Best regards,
Stefan Andersson
Tribal Media AB
Date: Thu, 26 Feb 2009 12:15:18 +
From: michaelwr...@yahoo.co.uk
To: opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
I still question if Global modules (that are really providing global
...@tribalmedia.se
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 11:59 AM
#yiv372014547 .hmmessage P
{
margin:0px;padding:0px;}
#yiv372014547 {
font-size:10pt;font-family:Verdana;}
I'm
Subject: Re: [Opensim-dev] Comms Manager
Hi,
note that I used IScene sxclusively?
Melanie
Stefan Andersson wrote:
Um, yeah, having 'Scene' as a type in anyhting outside of the Region will
lead to grief.
Suggestion:
--- OpenSim.Framework: ---
IGenericModule
by having
initialisation interfaces that are right for the task that the modules are
going to do makes sense.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 12:36 PM
I don't think Grid and Asset modules need to load into region
servers, and vice versa. At least not by the same interface. That
interchangeability makes other things
2009 3:00 AM
To: opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] Comms Manager
... did we not just come full circle?
I believe were all in agreement here, just varying on what to call stuff and
exactly what stuff they should be connected to.
I'm confident all that will sort
with them then I guess the answer is no. But I can see people
wanting to be able to access the GlobalRegistry from Region modules and
trying to do hacks so they can.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
the solution for everything.
So am trying to think of way of being more flexible.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26
flexible.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 1:14 PM
Hi,
one of the paradigms is that no Scene should
are
going
to do makes sense.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 12:36 PM
I don't think Grid and Asset modules need to load
the global registry
for now.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 1:36 PM
If you want to be more flexible, then my
wrote:
From: MW michaelwr...@yahoo.co.uk
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 1:48 PM
Well actually my suggestion of supporting multiple plugin interfaces allowed
both approaches and left everything up to the module creator
. Maybe at a later date we might decide to remove the
access to the global registry from the scenes (but at this time, I'm against
that)
--- On Thu, 26/2/09, MW michaelwr...@yahoo.co.uk wrote:
From: MW michaelwr...@yahoo.co.uk
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev
.
--- On Thu, 26/2/09, MW michaelwr...@yahoo.co.uk wrote:
From: MW michaelwr...@yahoo.co.uk
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 1:48 PM
Well actually my suggestion of supporting multiple plugin interfaces allowed
both
that loader.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 2:40 PM
I think that would introduce a layer of complexity
types could easily remove that loader.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 2:40 PM
I think
types). Its just not very clean to have to do extra trickery
in a loader to be able to load and register modules that don't need to have
references to IScene.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
clean to have to do extra
trickery in a loader to be able to load and register modules that don't need
to have references to IScene.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk
and requirements.
Thats why I would like to hear from other people.
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 5:28 PM
Well, here goes
MW wrote:
I'm not actually bothered about the interface per se. What I require is to be
able to
dynamically load generic modules that no where in that module does it know
about IScene/Scene.
That can be done with what you suggested
I actually see your approach as
, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 6:00 PM
Well, here goes
MW wrote:
I'm not actually bothered about the interface per se. What I
with what regions it wanted,
so would still need the Scene.RegisterModule() interface for
them.
--- On Thu, 26/2/09, Justin Clark-Casey jjusti...@googlemail.com wrote:
From: Justin Clark-Casey jjusti...@googlemail.com
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date
with what regions it wanted, so would still need the
Scene.RegisterModule() interface for them.
--- On *Thu, 26/2/09, Justin Clark-Casey /jjusti...@googlemail.com/*
wrote:
From: Justin Clark-Casey jjusti...@googlemail.com
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev
wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 8:50 PM
Yes, Sounds good. It will, of course, expose _all_ service modules to all
Scenes. If that is wanted in the long run
a
ApplicationPlugin that is a loader of IService modules. So these ideas are just
about how that loader handles things.
--- On Thu, 26/2/09, MW michaelwr...@yahoo.co.uk wrote:
From: MW michaelwr...@yahoo.co.uk
Subject: Re: [Opensim-dev] Comms Manager
To: opensim-dev@lists.berlios.de
Date: Thursday, 26
:
void RegisterPrimaryInterfaceT(T iface);
void RegisterSecondaryInterfaceT(T iface);
--- On Thu, 26/2/09, Melanie mela...@t-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday
-data.com wrote:
From: Melanie mela...@t-data.com
Subject: Re: [Opensim-dev] Comms Manager
To: michaelwr...@yahoo.co.uk, opensim-dev@lists.berlios.de
Date: Thursday, 26 February, 2009, 11:51 PM
Why is it that you want to have some fixed, hardcoded behavior instead of
leaving it to the module?
I thought
Hi,
MW wrote:
Again I never mentioned the Regions/Region modules accessing the core
at all. I said the Service modules would be able to use diferent
Registry methods to say if they should be added to the Scene Registries
or not. I'd say thats a step away from a hardcode behavior of having
Wonderful, marvellous, exactly what I always dreamed and prayed about. You are
my hero et c et c.
That gridservice registry will, in effect, be somehting like the 'shared
module' registry we've discussed before, so +1 on that fo sho.
On the topic of which plugins, and what specific class
Hi,
I'm against a CommsManager class, on the grounds I'm against most
other *Manager classes.
They serve as holders for stuff that seems straightforward
initially, but soon become monolithic molochs that make a simple
change, like adding a single method on a single interface, a task of
42 matches
Mail list logo
