Forum OpenACS Development: Re: How to handle dotlrn-specific changes in core?

22: Re: How to handle dotlrn-specific changes in core? (response to 1)

Posted by Caroline Meeks on 06/14/04 07:33 PM

I agree with Dave. Actions such as adding and removing notifications when a user is added or removed from a group is not a dotLRN specific need. What is .LRN specific is probably exactly what is added or removed.

Here is a non-.LRN use case, and I just consider this one of many possible use cases. On Aristoi I'm using subsites with bugtracker mounted for various clients. I'd like to set up bugtracker so that when a user was added to the subsite he was automatically subscribed to bugtracker and definitely I want the user to be automatically unsubscribed if he is dropped from the subsite.

Jeff, does COP do any sort of similar operations when a user is added/removed from a group?

23: Re: How to handle dotlrn-specific changes in core? (response to 22)

Posted by Jeff Davis on 06/14/04 07:50 PM

CoP does not currently do anything fancy on register/unregister/drop but it (like most everything else) should do sensible things when a user is added/removed.

I don't think anyone disputes the need to be able to do package/site specific things in such sequences, the only question in my mind is whether we want to do all this via service contracts (our only real callback mechanism right now) or with something lighter weight (or maybe fix service-contracts to make doing the lightweight version easier than it is now).

At a minimum I would like a version of the tcl binding acs_sc::impl::new_from_spec which did not store anything in the db and hence could be easily changed/upgraded.