Re: About X-JSON header and evil things... ;)

Thread: Re: About X-JSON header and evil things... ;)

Search this list only Search all lists
Re: About X-JSON header and evil things... ;)
	2007-01-25 22:15:29
> > I had thaught about a global AJAX.sanitizeJSON option. It certainly > > something we could implement at some point, but there are some > > potential issues with that (especially if you rely on some third party > > libs also using Prototype).That would be only a problem, if the third party module depends on > evalJSON() to not only return an object, but to also execute some > commands contained in the data, which makes the data not a JSON > structure in the first place and it is then an error to call evalJSON. Hi Martin, You're right. However, the only consistent way to do this in my opinion, is to have ALL defaults options available as a property of the Ajax object (Something similar to what script.aculo.us implemented for Effect), like so: Ajax.DEFAULT_OPTIONS = { asynchronous: true, sanitizeJSON: false, etc... } As this might have further implications, I believe it should dealt as a separate issue. But I agree with you, it would be a great feature. Best, Tobie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffsgooglegroups.com To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribegooglegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---