Forum OpenACS Development: Re: stable urls for all objects

Collapse
Posted by Tom Jackson on

What am I worried about?:

Can we go with having a service contract to figure out the local url to display an object that every package has to implement for every object type it provides?

As long as there is no requirement to implement this for every object, great.

I would think that every package instance could elect to not have its objects included in the search? If all instances of a package elected to be private, I would hope that the existence of the object types in that package would also remain private.

If not, this is just a back door to what was supposed to be a secure system.

Why, again, does this need to be in the core?

Collapse
Posted by Malte Sussdorff on
Why does this need to be in the core: Because I expect a couple of packages to rely on this. Furthermore, because at least one hopefully to become core package (categorization) relies on it. IMHO these are good arguments. But maybe we should start a discussion for guidelines when to include a package to core in the first place.
Collapse
Posted by Timo Hentschel on
Sure, if a package owner decides that his objects will not be available for search, notification and categories then this is perfectly fine to not implement the service contract and maybe even not to name the object (like in acs_named_objects - see other thread). I just assumed that most of the packages do indeed contain searchable and categorizable content so there would be a need for the search and categories package to display the object names and provide links to the objects. And I think that such functionality (object names and object links) should be provided by the core so that packages could rely on the interface to be there - if it is being used totally depends on whether the site-owner mounts the search or categories package.