Question

I have an application using ExtJS on the front end and TurboGears on the server. I am now started to add cookies to handle customisation front side using the CookieProvider state manager. This is cool but the cookies are passed on every call and these cookies are sizable. I have concerns about the performance hit.

Long and short, is there a way I can block certain cookies from being sent on calls to the server?

• Dave

Answer 1

Here’s a rundown of what I ended up implementing: All customisations are stored in a database. When a screen is being navigated to, I read the screen customisations for the current user and use it to initialise a simple memory based state provider in the init_component routine. The state provider listens for appropriate events and updates the in-memory state. The UI has a Preferences menu with and Save/Reset options. The save option saves the memory state to the server. Reset deletes the state from the database and rebuilds the screen with the default settings. This seems to work well.

FYI: other gotchas I found:

• grids don’t have an event for filter change
• combo boxes (amongst others) don’t have code to save state, you have to write your own.
• the state from grids is profligate (the original problem)

I implement one state setting per stateful control per screen, usually there is only one grid but one screen has a combo plus a grid. It probably would have been better to bundle them but lack of time…