[sakai2-tcc] Filtering Content served from CHS

[Aaron Zeckoski]

Ah, OK, so here is the use case I have in mind.
-----
I am system admin (or tool writer) and I need to add a custom bit to
the top of every page (like some CSS or JS). I don't want to have to
rebuild the system just to add a JS or CSS include but I can probably
manage something fairly straightforward like a provider or a config
option.
-----

It seems like something like this where I might create a filter and
include it with my tool would work EXCEPT that my filter might be
ignored. Then I get to spend hours explaining to people why the filter
I provided won't work with some other filter they made locally or
another filter provided by a 3rd party.

Maybe this needs a different solution where we setup something in the
portal and the default filter here will also respect the stuff the
portal is using but a system where my part that I added might just be
ignored seems like a maint nightmare.
Also, that detection of already provided stuff seems like it could be
a real pain when/if it fails and would be a maint burden on the core
Sakai team.

Am I mistaken on these?
-AZ


On Fri, Dec 10, 2010 at 10:40 AM, Matthew Buckett
<matthew.buckett at oucs.ox.ac.uk> wrote:
> On 10 December 2010 15:24, Aaron Zeckoski <aaronz at vt.edu> wrote:
>> But if we chain it won't we end up with something like this for 3
>> things in the chain?
>
> Yep, firstly my current implementation checks so would only append the
> top/tail if it doesn't see one already.
>
> Second I would see each filter as performing a separate function, so
> you have one filter which does the top/tailing, and a different filter
> which performs some other function (autoexpanding links
> http://news.bbc.co.uk -> <a
> href="http://news.bbc.co.uk">http://news.bbc.co.uk</a>), the other
> filters don't add HTML top and tails.
>
> --
>   Matthew Buckett
>   VLE Developer, LTG, Oxford University Computing Services
>



-- 
Aaron Zeckoski - Software Engineer - http://tinyurl.com/azprofile