I’m back
I haven’t posted much lately, because I had my exam session, but it’s finally and completely over and done. Now there has been a lot of activity on my favorite topic, Ajax, lately and I had a hard time keeping up with all the news that from Ajaxian, and many others. Especially the discussion on wether graphical drawing is a good thing for the client side has some interesting points:
Client side drawing is possible thanks to many possible implementations but it has neither a good standardized API nor is it very reliable.
On the other hand a nicely written article on the concepts of REST and Ajax has caught my eye:
So this is about it to catch a bit up with the present, after hammering my head against all those Analysis and Linear Algebra Books, sorry if it is a bit superficial, but hey, there is just too much to write about now to dwell in the past.
Technorati Tags: exam, java, REST, ajax
Client side drawing is possible thanks to many possible implementations but it has neither a good standardized API nor is it very reliable.
On the other hand a nicely written article on the concepts of REST and Ajax has caught my eye:
Javaâ„¢ Servlet’s HttpSession API provides an example of this strain.
HttpSession lets you associate session state with a particular user.
This API seems deceptively simple to novice developers. Indeed, it
appears that you can store any object in HttpSession and pull it out
without ever coding any special lookup logic yourself. But as you start
putting more objects in HttpSession, you start to notice that your
application server uses more and more memory and processing resources.
Soon you decide that you need to deploy your application in a clustered
environment to help with growing resource needs. Then you realize that
for HttpSession to work in a clustered environment, each object must
implement Java’s Serializable interface so that session
data can be transmitted between servers in a clustered environment.
Then you must decide whether or not your application server should
persist session data in the case of a shutdown/restart cycle. Soon you
begin to question whether violating the client-stateless-server
constraint was such a good idea after all. (Actually, many developers
are ignorant of this constraint.)But more on this in a separate Post So this is about it to catch a bit up with the present, after hammering my head against all those Analysis and Linear Algebra Books, sorry if it is a bit superficial, but hey, there is just too much to write about now to dwell in the past.
Technorati Tags: exam, java, REST, ajax
