> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Derick Rethans > Sent: 26 June 2008 14:30 > To: Components > Cc: Public SDK List > Subject: Re: [Components] MmvTools requirements and design > > On Wed, 25 Jun 2008, Derick Rethans wrote: > > > James and I (as well as others through meetings), have been working > > the past days on the MvcTools component and design. The > fruits of this > > labour are now in SVN[1]. We'd like you to ask to look at this and > > provide feedback. > > > > [1] > > http://svn.ezcomponents.org/viewvc.cgi/experimental/MvcTools/design/ > > After going through your comments, we've updated the > requirements and design documents. You can see the differences here: > > http://svn.ezcomponents.org/viewvc.cgi/experimental/MvcTools/d > esign/requirements.txt?r1=8470&r2=8481&pathrev=8481&diff_format=h > http://svn.ezcomponents.org/viewvc.cgi/experimental/MvcTools/d > esign/design.txt?r1=8472&r2=8482&diff_format=h > > and the full documents, including new updated diagrams are at > the same location [1] again. > > regards, > Derick
The other thing I'm trying todo is get the system to automatically maintain various headers during GET requests. Like testing/accessing any request variables not from the url, (Accept-*, or cookies) means you have to add it to the response Vary header. Accessing cookies, like seeing if the user is logged in, probably means to send Cache-Control: private header. Also trying to maintain the rest of the Cache-Control directives, using a similar idea to ESI (http://www.edge-delivery.org/overview.html) Basically have each component in the response have its own (sub-)set of http headers. So default headers would be for example, Cache-control: public, max-age=86400, and no Vary header. Then as the response is being built they would be altered if need, either because of Vary, or to reduce the max-age. Jared -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
