I did some more digging and found that the TG2 startup code does not
pass any external parameters on to toscawidgets middleware, it passes
a fixed set of parameters into toscawidgets.makemiddleware.

With a few judiscious edits I have made it pass in anything with
toscawidgets.middleware and toscawidgets.framework from the ini file
(base_config) and so passed resources_expire in to the middleware for
use in tw.core.resources.py which allready looked for a cache expiry
value. This way all the javascript files get a cache time in them. I
have done this as there is a large amount of javascript included for
the tgext.admin.AdminController (Catwalk,Rest) that makes the admin
interface very slow in development. (I am running it using paster
serve).

But on the whole very impressed with TG2 over TG1. 2 gold stars.

Edits where done in turbogears.tg.configuration.py to include relevant
config values in the values passed to tw_middleware
And in toscawidgets.tw.core.middleware.py to save expires and add to
environ during a call. If interested I will generate patch files and
post where requested.


On Mar 5, 1:30 pm, Paul Johnston <[email protected]> wrote:
> Hi,
>
> > Static files served from the public directory are allowing caching and
> > even get not changed responses.
>
> Yep, that's the best 
> approach...http://toscawidgets.org/documentation/ToscaWidgets/deploy.html
>
> Paul
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to