Digital Web had a short but worthy interview of Jeremy Keith — author of DOM Scripting
He’s got a new book out about writing Bulletproof AJAX…if it’s as good as Bulletproof Web Design by Dan Cederholm, then it’ll make my life easier.
The XMLHttpRequest Object specification defines an API that provides scripted client functionality for transferring data between a client and a server.
Documenting changes since Last Call, the Web API Working Group has released an updated Working Draft of “The XMLHttpRequest Object.” The core component of Ajax, the XMLHttpRequest object is an interface that allows scripts to perform HTTP client functions, such as submitting form data or loading data from a remote Web site. Read about the Rich Web Clients Activity.
Read more about AJAX programming from Wikipedia and Rich Web Clients page at W3C.
There’s a new (published May, 2007) book about web application security “Cross Site Scripting Attacks: XSS Exploits and Defense” written by Jeremiah Grossman of WhiteHat Security, Inc.
“Gartner Group has stated that today, over 70% of cyber attacks occur at the Web (or website) application layer.” — whitehatsec.com.
Jeremiah Grossman has been recently named one of InfoWorld’s Top 25 CTOs.
As a web developer and UI designer, web application security is rapidly becoming a necessary skillset to have in your online arsenal during web application development. It is said that XSS (Cross Site Scripting) is the new “buffer overflow” and malware (malicious software) delivery can perpetuate through a vulnerable web site and a deviously crafted URI — giving rise to the popularity of online “phishing” scams and other potentially dangerous exploits.
Along with rise in popularity of AJAX on the web, there have been a few cool applications I have seen and many lists with more “cool AJAX” sites.
More “cool AJAX” lists:
You can bypass free registration with the Bug Me Not Firefox extension.
Took me a google search to find this one, but for some reason one of my forms was not submitting using javascript.
The reason was the statement “formObj.submit();” in the javascript was colliding (resulting in ambiguity within the browser) with the form button, which was also named “submit”.
ie:
Change the name of the button to “login” or something else more reflective of it’s functionality instead of “submit”.
javascript:
function submitForm(formId) {
var formObj = document.getElementById(formId);
formObj.submit();
}
html:
Login