Peter Haza wrote:
Hi
1. Your counter is an external javascript and is out of radiant's
control whatsoever because it is the client(browser) calling the
script, not radiant(server).
A possible solution to this is to make radiant(server) make the call,
but that would probably require some ruby/rails programming.
2,3. I would believe these would be cached, as I presume they use a
feed /aggregator that is caching the results, but don't quote me on this.
Best to wait and see if someone else can give a definitive answer.
It's important to notice the difference between 1 and 2,3.
Whereas 1 outputs javascript, the dynamics happen on the client
side(browser) and out of radiant's control,
while 2,3 does the magic on the server side (hence it's cachable by
radiant)
So bottom line if I am correct:
1. Unaffected by caching
2. Affected
3. Affected
ph
Thanks Peter,
That ties with my understanding also. I do hope that I'll get another
response.
While we're at it, would IFRAME help? I've heard that word thrown
around from time to time and I haven't yet got around to checking it
out... or how to use it from within a Radiant site at this stage.
Cheers,
Mohit.
3/30/2008 | 8:34 PM.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
