Previously Balazs Ree wrote: > > kss.plugin.cacheability is a transitional package that brings you > cacheable KSS requests for version 1.4 and trunk, today. > > The work was fully sponsored by Zest Software. > > Cacheability allows you to use GET KSS requests, instead of the POST > request, that KSS currently uses. > > GET requests in KSS are planned and hopefully arrive in the next > major version. Meanwhile this package provides transitional access to > this feature. > > The plugin javascript uses some unpublished parts of the KSS core. We > will need to provide a clean API as well, for similar tasks in the next > version. So the plugin code should not be considered as an example, but I > encourage its usage. I will provide an upgrade path, once the feature > lands in KSS. > > To summarize the main usage, you can make a server action as GET request > this way: > > css:event { > action-client: cacheability-serverAction; > cacheability-serverAction-url: actionName; > } > > The future syntax for this will be (once it lands in trunk): > > css:event { > action-server: actionName method(GET); > } > > > POST records will always stay the default method in KSS, as the GET > method you must only use with such server actions that are guaranteed to > make no changes to the content.
This begs the interesting question: what infrastructure is there to control caching (Cache-Control, Expires, IMS-request, E-Tags, purges) for those requests? Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Kss-devel mailing list Kss-devel@codespeak.net http://codespeak.net/mailman/listinfo/kss-devel