The short version of this is pretty easy to see, all of the browsers except for Firefox will use at least 2 packets for an XHR done over HTTP POST. When I saw that Safari sent 2 packets I figured that Chrome would as well, but I tested it anyway just to make sure.
OpenStreetMap.org’s RESTful API allows anyone to access data on their continually growing collaborative map of the world… in XML. This is great for most applications, but if you’re working in JavaScript (as we are), XML might as well be greek. We need JSON.
]]>
SpellCheck est une classe permettant d'intégrer un correcteur orthographique dans vos pages. Il fonctionne aussi bien avec des inputs html standard (input, textarea) qu'avec des éditeurs basés sur des iframes (dijit.form.Textarea, dijit.Editor, etc...)
MenuGenerator est une classe qui permet de générer un popup menu (pour bouton dropdown ou menu contextuel ou autre) à partir d'une représentation objet. La structure de l'objet est utilisée pour gérer la création de menus simples ou arborescents.
]]>
Maybe it's time to test cross-domain xmlhttprequest in Firefox 3
FileTreePanel is client-server application where client (browser) provides the user interface (UI) which displays the tree and context menu, handles drag & drop operations, etc. The filesystem that is displayed and managed by the UI is stored on a server. Therefore, we need some communication layer between client and server. Client sends a command to server, server processes this command and responds with a result. Client in turn processes the response and display results. All this communication is running in the background by Ajax (XMLHttpRequest) calls. The XMLHttpRequest is not used directly but the Ext JS - JavaScript Library ajax layer is used for this purpose. Client requests data from server with standard POST method and server is expected to respond with JSON (JavaScript Object Notation) string and appropriate HTTP headers.
]]>This is not a compliance or conformance test suite; an implementation can fail many of the tests here and still be HTTP conformant. Instead, the idea is to show what HTTP mechanisms different implementations support, and how they support them, since many aspects of these libraries are underdefined. Each group of tests explains what is being tested and what the implications of failure are. Although many of the tests are automated, some may require user interaction, via a "run test" button. Be sure to follow any instructions carefully.
]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>
]]>