2009/6/7 Mark Renouf <[email protected]>: > > On Jun 5, 12:49 pm, Piotr Jaroszyński <[email protected]> wrote: > >> One thing that I think would be nice to do is to look at the HTML 5 cross >> site xhr implementations and use them where available and only fallback to >> this solution on older browsers. > > This would be a nice approach, especially if you could abstract it > enough so it you would automatically be upgraded to using standards- > base methods in the future without changing any of your project.
Yeah, that's the idea. >> Security-wise I think it can match the w3 spec - at least for GETs and >> POSTs (other methods are not supported in GWT anyway because of the >> safari bug). The server would be required to send the access control >> headers then, but that's a good idea anyway as it will be required >> for the new cross site xhr anyway. > > Hmm. It's a shame that Safari bug is only reason for that. AFAIK it > was fixed QUITE a while ago. We do GET/PUT/POST/HEAD/DELETE from all > the major browsers just fine (by sub-classing RequestBuilder). I will look into that but with PUTs and DELETEs it gets a bit tricky (need to do preflight requests). -- Best Regards, Piotr Jaroszyński --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
