Gabriel, The stanard solution is to just rely on the session, though I can see your point of that mechanism not always being sufficient.
I've created a JIRA issue to track modifying the client such that you can plug in your own method for determining the Gatewaying: http://www.ja-sig.org/issues/browse/CASC-58 In the meantime, you could probably modify the client to use a cookie instead of the session check if you wanted. -Scott On Mon, Jun 16, 2008 at 11:49 AM, Gabriel Falkenberg < [EMAIL PROTECTED]> wrote: > Hi! I have a question regarding caching in combination with users that > are not logged in and the gateway feature of CAS. > > * I have a site which relies heavily on caching for users that are not > logged in > * I don't want to redirect to CAS at every request > * I don't want to create a session since my environment isn't able to > cache when a session exists > > Is there a standard solution for this? > > Best regards > Gabriel Falkenberg > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
