Skip to main content

It's been a while since I posted

It's been a week since I posted last. I am really sorry, this is the second time in succession that I have missed my target of posting at least thrice a week. By way of an excuse, all I have is a lame "it's been a bit crazy at work". I am messing around with a lot of client side technologies, like AJAX and the plethora of libraries that accompany it, and all this without really understanding Javascript well enough.

One of the libraries I am checking out is DWR (Direct Web Remoting) . It allows Javascript code to invoke Java objects. All this is done by creating proxy objects in Javascript that make AJAX calls to the DWR Servlet, which in turn invokes the Java objects. I personally think, it's a very nice concept, and it also supports reverse AJAX.

Would you like to know more about DWR? Please comment and let me know. I will then post a series on DWR after completing the current one on Unicode characters.

 

On a total tangent, here's a little something from Doc Searls on writing to inform readers


 

I don’t think of my what I do here as production of “information” that others “consume”. Nor do I think of it as “one-to-many” or “many-to-many”. I thnk of it as writing that will hopefully inform readers.

 

Informing is not the same as “delivering information”. Inform is derived from the verb to form. When you inform me, you form me. You enlarge that which makes me most human: what I know. I am, to some degree, authored by you.

  What we call “authority” is the right we give others to author us, to enlarge us.
  The human need to increase what we know, and to help each other do the same, is what the Net at its best is all about. Yeah, it’s about other things. But it needs to be respected as an accessory to our humanity. And terms like “social media”, forgive me, don’t do that. (At least not for me.

 



Note: This text was originally posted on my earlier blog at http://www.adaptivelearningonline.net
Here are the comments from the original post

-----
COMMENT:
AUTHOR: kishore hariharan
URL:
DATE: 08/29/2007 05:33:38 AM
hi prof,
this concerns the simple yet powerful concept of DWR. My current assignment involves working and exploring the same. I and two of my colleauges actually implemented server side push concept using DWR, as the client demanded real time updates for his Stock Trading Application.
The POC took a while but we managed to finish the implementation with support from JMS.
There are still a few grey areas on using this:
- like the number of live connections DWR can handle at an instance.
-How does DWR actually manage to keep the connections alive is still a mystery. The best we figured was that it sent some heartbeats at frequent intervals. Still not very clear on this.
-Can it really manage to bypass poweful firewalls.
These are a few of the questions we are still researching on. The implementation at the moment works great but still awaits the real test of volume testing.

-----
COMMENT:
AUTHOR: Parag
DATE: 08/30/2007 10:57:23 AM
Kishore,

These are interesting topics you are researching. I am sure your findings will be of interest to many people.

Do post them to our forum.

--
Regards
Parag

Comments

Popular posts from this blog

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- prismnet.com As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other