Focusing on API for server-side transport layer and authentication, Vibe Protocol 3.0.0-Alpha8, Vibe JavaScript Client 3.0.0-Alpha8 and Vibe Java Server 3.0.0-Alpha11 are released.

• API for server-side transport layer is added. Accordingly, how to bootstrap server is changed. vibe-protocol#45
  • httpAction and wsAction are removed from Server and Server itself becomes Action<ServerTransport>. vibe-java-server#68
  • As a replacement of httpAction and wsAction, HttpTransportServer and WebSocketTransportServer are added. vibe-java-server#71
• The extension, one of building blocks of the protocol, is dropped. vibe-protocol#48
• It is decided that authentication should be done by documentation and examples without adding special API. vibe-protocol#25

As now only three main features, attribute support, event cache and binary event, are remaining in alpha phase, we think beta should be available in late Feb. In next iteration, attribute support will be covered, which allows you to set and get attribute to and from server regardless of clustering and accordingly can be used to provide user session. If you have any feedback, please let us know and we really appreciate them.

Focusing on enhancements of longpoll transport and so on, Vibe Protocol 3.0.0-Alpha7, Vibe JavaScript Client 3.0.0-Alpha7, Vibe Java Server 3.0.0-Alpha10 and Vibe Java Platform 3.0.0-Alpha8 are released.

• Use of unnecessary message format in longpoll transport is removed. vibe-protocol#47, vibe-javascript-client#41, vibe-java-server#70
• When the underlying connection of longpoll transaport is terminated, it fires close event immediately. vibe-protocol#46, vibe-java-server#70
• Now transport underlying socket and resource underlying transport are accessible through through unwrap method. vibe-java-server#67
• finishAction representing the end of the response is added and accordingly now closeAction is called only when the underlying connection is terminated. vibe-java-platform#39

In next iteration, authentication will be covered as you have noticed. If you have any feedback, please let us know and we really appreciate them.

For the last day of 2014, Vibe Protocol 3.0.0-Alpha6, Vibe JavaScript Client 3.0.0-Alpha6 and Vibe Java Server 3.0.0-Alpha9 are released. At first, we tried to design interfaces to make use of transport layer e.g. to build another protocol on top of transport layer but it took so much time so we decided to do that on beta. However, now that Transport is a public interface, you can do that by referring current implementations.

• transports option is replaced with URI and accordingly vibe.open's new signature is introduced to accept multiple URIs. vibe-protocol#44, vibe-javascript-client#38
• org.atmosphere.vibe.server package is renamed to org.atmosphere.vibe. vibe-java-server#66

In next iteration, how to authenticate will be covered. If you have any feedback, please let us know and we really appreciate them.

Focusing on reorganization of module and package structure for further better extension, Vibe Java Platform 3.0.0-Alpha7 is released and accordingly Vibe Java Server 3.0.0-Alpha8 is released as well.

• Module name and package name are reorganized. vibe-java-platform#35
  • vibe-platform-server module decomposed into vibe-platform-action, vibe-platform-http and vibe-platform-ws.
  • o.a.v.p.server package decomposed into o.a.v.p.action, o.a.v.p.http and o.a.v.p.ws.
  • vibe-platform-server-atmosphere2 module renamed into vibe-platform-bridge-atmosphere2. The same for all the other bridges.
  • o.a.v.p.server.atmosphere2 package renamed into o.a.v.p.bridge.atmosphere2. The same for all the other bridges.
• Now ServerWebSocket returns void on close method. vibe-java-platform#38

This release will probably be a last alpha of Vibe Java Platform. If you have any feedback, please let us know and we really appreciate them.

Focusing on the transport calculation, Vibe Protocol 3.0.0-Alpha5, Vibe JavaScript Client 3.0.0-Alpha5 and Vibe Java Server 3.0.0-Alpha7 are released.

• Now transport's availability is calculated by try and error as well as by feature detection. Therefore, given environment if one of transports can work, it will really work automagically so from now on you don't need to even know what transport is. vibe-protocol#14, vibe-java-server#63, vibe-javascript-client#37

In fact, this feature is one of issues derived from making transport public we are focusing and will focus on. If you have any feedback, please let us know and we really appreciate them.