On 1/29/07, David Huynh <[EMAIL PROTECTED]> wrote: > Good point about minimum namespace clobbering. I have a feeling that > little client-side code has a global variable called "database" right > now, but then I haven't built many 3-tier web apps.
It's probably an uncommon and mostly easy to bypass issue; I only take notice of it for deploying Exhibit dynamically pan-web in environments where any variable name, particularly in the English language (or short), is likely to occur once in a while, and two exposed variable names (more or less) double the collision risk. > > Similarly, once Douglas Crockford's JSONRequest (RFC 4627, > > http://rfc.roxen.com/4627) gets widely deployed / promoted to internet > > standard, we will also overcome the JSONP hack. (I'd guess that will > > happens sooner, but hopefully that we'd get browser native "database" > > eventually too.) > > How do you see RFC 4627 helping us out? I was referring to the callback > trick that Google Data API uses so that it can pass data cross-domain. Ow, my bad. The document I thought I referred to -- http://www.json.org/JSONRequest.html -- wasn't actually an RFC. JSONRequest's core idea is to be a cross-domain capable mechanism to get and post JSON data without involving the smudge of passing callback names in the data layer. > Awesome. Should we carry on some design discussion on [EMAIL PROTECTED] or > ... ? I should apparently join dev, for one thing, but that suggestion sounds like a good idea, too. :-) -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
