Of course the content has some restrictions: one can't create an
AjaxUpdateContainer (or anything else that requires a JavaScript id)
inside it. But the pager is just links and sugar, so I think that
wouldn't be a problem.
Any more potential problems I'm missing? :)
Let me see ... making your life overly difficult :) ?
You're going to have component actions in there mixed with Ajax
Updates ... If one of those pagers updates in an Ajax update without
the other cached one updating, you'll end up with each pager generated
from different contexts and the one not updated may be now referring
to a context that no longer exists.
I still maintain that easier = better here ... You aren't really
trying to cache the HTML, you're trying to cache the query results. a
PaginationState class that you pass into both, the first filling it
out, the second see it's filled out be a lot less error prone.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
