View source

(Placeholder wiki page. No content yet.)

This wiki page is meant for gathering a list of candidate Ajax best practices. 
This page is one of a series of wiki pages that collect candidate Ajax best practices
broken down as follows:

* [[Best Practices Applications]] - Best practices for Ajax applications (i.e., the software developed by the Ajax application developer, who is likely to build his application using an Ajax toolkit)
* [[Best Practices Browsers]] - Best practices for Web browsers so that they support Ajax and OpenAjax in an optimal manner
* [[Best Practices IDEs]] - Best practices for IDEs that support Ajax developments
* [[Best Practices Libraries]] - Best practices for Ajax JavaScript runtime libraries
* [[Best Practices Servers]] - Best practices for server frameworks that produce Ajax-powered user interfaces


= Approved Best Practices =

Note: the official list of approved best practices probably will be located somewhere else, perhaps on the public part of , but we haven't decided on the location yet.


= Candidate Best Practices =

This section is meant to capture candidate best practices that at least one Member believes we should evangelize to the browser vendors. This list has yet to be discussed and approved by the rest of OpenAjax Alliance.

== Content identification ==

This will describe recommendations for setting HTTP headers and markup such that the content will work well with today's browsers. These recommendations will codify and document existing practice among leading Ajax developers today. For example, we mgiht recommend what DOCTYPE to use.

== JavaScript techniques ==

* Do we want to have a best practice that tells developers to avoid for(in) on arrays and instead use for(;;)? This would be to deal with the reality of the industry that lots of toolkits include prototype.js and prototype.js overrides the array class which causes for(in) on arrays to not work as expected.

(We are just beginning. Much more to come later.)