Peter De Berdt wrote: > On 27 Oct 2008, at 21:44, Chris Dekker wrote: > >> >> alternative measures involving an extra call to the server. > And how about instead of abusing cookies for something they weren't > made to do, doing the following: > > <div id="here-is-all-my-nifty-positional-data" style="display:none;"> > ... > </div> > > • No cookie abuse (that's not what they're there for, they were made > for persisting data across requests and site visits, not for passing > in data) > • No 3KB data limit > • Same behavior > • In case it matters: indexable by google and other search engines > > > Best regards > > Peter De Berdt
Thanks for your input but your solution isnt really an applicable option. I know cookies aren't there for what I wanted to do. It is a great way to serve meta data with the image tiles at the same time though. Since Google Maps API handles all the requests for the tile, there is no way to come inbetween there to fill some div with my JS data like you suggested. If you have a practical example I'd be very glad to see it. The data for each tile is very specific and based on several parameters hashed to a tile name. So indexing by Google is unwanted even. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
