Name: Shankar
Yahoo IM:
In a series of blogs I will deal with different aspects/features of JBoss AS7. This is first blog of the series. In this blog I will discuss a new feature in AS-7 called Managed Domain. After reading this blog readers should have good understanding of the managed domain, its use and advantages.
soapUI is one of the best tools for testing the REST services. It can very efficiently help to check and ensure that the services return just what is expected. Due to these promising reasons we tried to use soapUI for testing the REST based services of our application. But we found a serious road block. The REST services in our application is secured by OAuth 1.0, and as of now soapUI has out of the box support for basic authentication only.
There is a lot of buzz all around - 'WebSocket is quicker'. But why WebSocket is quicker? As you read this blog this question should get answered.
When we say WebSocket is quicker the comparison is always with HTTP. So before we start discussing WebSocket protocol let us talk about HTTP.
In this blog I will discuss in detail the process of handshake in WebSocket Protocol. The first step in WebSocket communication is the formal handshake between the client and the server. The discussion is based on the latest specification released on 16th August 2010 by I. Hickson. I will deal in detail the request and response headers and also discuss the why aspect.
If reader is more interested in getting started with WebSocket you may read the blog - Web Socket Communication Using jWebSocket.
Web Socket has been introduced in HTML5 to enable full duplex communication with minimum network traffic and latency. I was working on a PoC on HTMl5 Web Socket. In this blog I am sharing my experience about working with jWebSocket to get the basic WebSocket communication running. jWebSocket is pure Java/JavaScript based implementation for implementing Web Socket communication. After reading this blog the readers should be able to send asynchronous request from client through Web Socket and get response from the server. This blog assumes that readers have basic knowledge of HTML5 Web Sockets
HTML 5 Web Socket specification defines an API that enables full duplex communication over one (TCP) socket. Before web sockets the server could respond only on receiving a request from a web client. To overcome this limitation the common workarounds are polling, long polling and comet based solutions. HTML 5 Web Sockets comes as an inbuilt support for bi-directional communication which promises to be highly scalable due to reduced network traffic and latency.
Read more »
