Now I’ve seen everything, holiday Ajax jingles:
[All I want for Christmas is Ajax
I don’t want a tall skinny tree
or lots of presents under it.
All I ask for are some Web 2.0 goodies
that are zipped and not wrapped.
I want PHP and not PAJAMAS.
Give me widgets and not gadgets.
Give me a torrent of flashy de.
The “Real-World AJAX One-Day Seminar” is scheduled for Monday, March 13th 2006 in New York City. There are some huge names that are going to be speaking at this seminar:
This one-day AJAX seminar will feature 15 speakers in 11 sessions, including the world’s most renowned AJAX experts: Jesse James Garrett, the Father of AJAX; David Heinemeier Hansson, the creator of Ruby on Rails (with his very first talk on “AJAX in Rails”); Satish Dharmaraj, the creator of server-side Java; Bill Scott, AJAX evangelist of Yahoo!
I came across an page talking about AHAH (Asynchronous HTML and HTTP). I’ve already done an article on this, but this one caught my eye because of his mention about security.
He makes an interesting observation about people with criminal intent. With Ajax a hacker only needs to fake a domain name once. He can then fake browser activity by using Ajax to “refresh” the entire HTML body. Can we say phishing?
Yakov Fain wrote an interesting article: A Cup of AJAX? Nay, Just Regular Java Please at SYS-CON DEUTSCHLAND.
I can agree that big Internet guys [Google] can and should invest some serious dough into supporting screen-refresh-on-mouse-move in HTML-based screens. But when it comes to a regular Intranet business application, when the users/browsers/platforms are known and when the cost of the project development matters, Id stay with a fat client written in Java, or (if you like a fancy GUI) Macromedia’s Flash or Flex.
There has been a lot of buzz about this book, Ajax in Action. I do plan to buy it, or rather get my boss to purchase it for the office :), so I haven’t read it yet. Considering all the reviews it’s been getting, I’ve decided to alert you guys about it. Maybe one of you could purchase it and send me a review.
Happy Reading.
Ok, by now I’m guess that we all know what Writely. It’s a wonderful little Web (AJAX) based word processor. Does almost everything that Microsoft Word does and even some things it doesn’t (PDF creation).
The guys over at TechCrunch have done an article on it. There have been many blogs entries on Writely, but this one struck me because of the comments on it. Some people are downplaying what the Writely team has produced here.
I found this link somewhere, I can’t remember where. But Li Shen has packaged a nice AJAX wrapper called AJAX Client Engine (ACE). I downloaded it and took a look at it and I must say, it is quite functional. I took a look at his source code and found it to be relatively clean. It’s not too bulky making it a nice thin wrapper and he made it very object oriented.
With the way that Ajax applications have been developing, the questions of whether these applications can completely replace PC software comes to mind. Take Writely (online word processor) for instance:
“People are e-mailing document attachments in order to collaborate or else, in the enterprise world, they are attempting to use wildly expensive and complicated systems - the equivalent of trying to pound in a nail with a sledgehammer,” says Jen Mazzon, Writely’s vice president of marketing.
I came across an interesting article at CRM News that spoke a little' bit about online shopping for this upcoming Christmas season.
RIAs are beginning to pop up all over the e-commerce world, with some notable examples being Gap, Nike (NYSE: NKE), and L.L. Bean. So far the use of AJAX and RIA in online retail tends to be limited to marketing “microsites,” usually built in Macromedia (Nasdaq: MACR), which enable customers to explore a new product but not purchase it; and also for “guided selling” applications that provide some extra help in choosing the right product.
I believe that I now need to rethink the Ajax sequence on the project I am working on for work. As it stands, I had to do some interesting tinkering to make things work and emulate the console side properly. A normal sequence of GETs and POSTs would have been sufficient, except I needed something to handle server pushes. In the console application, there are some instances like popup boxes. Eg.