Thanks for the input and ideas. The servlet approach seems to have potential but I think because our company will be the only users of the taglib I'm going to force the user of the lib to paste a special taglib folder into the context.
It would be really cool if there was a standard that made it possible for a taglib author to specify a folder in the jar that they want to make available off the context but I could see how it would create some security concerns. ----- Original Message ----- From: "Rahul P Akolkar" <[EMAIL PROTECTED]> To: "Tag Libraries Users List" <taglibs-user@jakarta.apache.org> Sent: Tuesday, April 19, 2005 4:44 PM Subject: Re: packing images and style sheets with a taglib > > It also means you have to deal with cache > > headers, so that you're not serving up the > > same images to the same browser again and again. > > Very true, cache, response-type, in short, you have to behave like a good > web server ;-) However, its definitely manageable, and by pulling some of > the overhead upon the taglib author, it aims for taglib user convenience. > OTOH, the vanilla solution seems to be an auxillary resource bundle (not > in the i18n sense) users need to download and plop into each app/war. So. > > -Rahul > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
