[sldev] Re: Plugin architecture

Jesse Nesbitt mindtriggerz at gmail.com
Thu Feb 22 09:21:01 PST 2007


I did in fact get my threads crossed >.<
Sorry!
As I see it, it's a courtesy feature, and the plugin could be
re-enabled by the user after it was automatically unloaded, but most
people care about the grid :P

On 2/22/07, John Hurliman <jhurliman at wsu.edu> wrote:
> The original post on plugin invalidation was talking about runtime
> loading/unloading of plugins and had nothing to do with throttling or
> server-side code, I think you might have got sub-threads crossed. The
> mention of a server-side throttle was made by the same person you are
> responding to.
>
> Jesse Nesbitt wrote:
> > It's a throttle, and as such it's server side.
> >
> > On 2/22/07, dirk husemann <hud at zurich.ibm.com> wrote:
> >> Mark Wagner wrote:
> >> > On 2/21/07, Ben Byer <sldev at bushing.mm.st> wrote:
> >> >> On Feb 21, 2007, at 5:55 PM, soft at softnoel.org wrote:
> >> >>
> >> >> > [...] and LL-triggered plugin invalidation possible.
> >> >>
> >> >> Whoa.  Everyone, raise your hand if you think this is a good idea.
> >> >
> >> > Certainly.  Particularly once the server code is open-sourced, it
> >> > would be nice for a server to be able to say that certain plugins
> >> > can't be used with it - say, an av scanner in a combat sim.
> >> what exactly prevents me from running a client that just ignores this?
> >>
> >>    cheers,
> >>    dirk
> >>
> >>
> >
> >
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>


-- 
--Jesse


More information about the SLDev mailing list