David Black [2011-07-20 21:08]: > What's odd is that both behaviors seem to happen: the Ruby > variables being bound to the literal GEO strings, and the Ruby > variables being bound to the ESI interpolations of those strings. no, it's not. the ruby variables are replaced with the string values you initialized them with - in *both* places. the ESI processing kicks in *after* that (it operates on what the application sends as HTML response; just like SSI in principle). so there's nothing unusual going on at all. it's just that both processors (ruby/erb and ESI) operate in the opposite order than you seem to have assumed.
but now that you found a different solution this is all moot, of course ;) -- 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.
