Node is tested on Linux, Macintosh, and Solaris. It also runs on Windows/Cygwin, FreeBSD, and OpenBSD.
Node tells the operating system (through epoll, kqueue, /dev/poll, or select) that it should be notified when a new connection is made, and then it goes to sleep. If someone new connects, then it executes the callback. Each connection is only a small heap allocation. – nodejs
If you are familiar with the embedded browser in the Lotus products you may or may not have heard of BrowserFunction, most likely not! The problem is this class is not very well documented and was part of E4 and is scheduled for Eclipse 3.6. Notes 8.5.2 does however support this SWT class so you can begin to play with it once 8.5.2 is available.
The Attachment viewer is such an application, you can check out the code on OpenNTF. I don’t use the BrowserFunction in the OpenNTF version but I have already begun to make an Lotus Notes 8.5.2 version of the plugin that has much better integration with the Notes client. If you are writing side bar plugins and want to standardize on writing in a single technology you should check out the SWT Browser and the BrowserFunction support.
I chose the REST service to emit JSON because it makes it very easy to process on the client. Check out the Dojo code below that creates a session with the “Base” servlet and then processes the response as a regular JS object, in this case “session = dojo.fromJson(response);“:
“Duck typing is based upon the saying that if it walks like a duck and quacks like a dck, then its a duck.”
Ok, I don’t really have any authority or any involvement whatsoever with jDojo but I figured I would introduce it on my site. I am going to be checking it out more closely going forward and seeing what benefit it really gives us.
You will need to register to get into the jDojo site so go ahead – I think it is well worth it. The latest version now has support for Dojo 1.4 – which tells me these guys are making sure the community has the ability to support very current API’s. I didn’t get to see the EclipseCon session Michael gave but it looked very interesting and also gives a great summary of what jDojo is.
The benefits in summary..
The JDojo programmer can now write its Web UI code using the features of the Eclipse Java tooling.
Type information is now part of the code, and not of the documentation anymore.
The programmer still deals with the DOM, browser environment etc, having the full control over all the details.
Existing code can be easily integrated by writing a JDojo stub for it.