//AMIS Technology Blog » kaazing

Posts tagged kaazing

WebshopsupportApp

How to build an IM (XMPP) solution with Oracle APEX and Websockets

0
7 months ago
by Andre_Verbeek in , , , , , ,
Using Kaazing Websocket Gateway and OpenFire Scenario: If you, for example, have a webshop and a webshop online support application for internal use, this solution will let the webshop customer call in some help by using IM. The support application will react on the customer call by opening the support application with customer details selected and the messaging client opened. I used an Apex application to create both parts of the solution. The IM client however is easy to integrate in any kind of website/framework.

 

Underneath the recipe for some nice IM functionality in Oracle Apex, assuming you have a running Apex instance and a JVM 1.5+ install) and moderate+ Apex skills:
  1. Scrape together the ingredients
  2. Install Kaazing Gateway XMPP edition and OpenFire
  3. Configure Kaazing and OpenFire
  4. Create an Apex app with IM client
  5. Create anApex Webshop support app
  6. Wire the Apex Webshop support app to the Apex app with IM client
  7. Final touch
After finishing this step-by-step recipe your application looks like this: The webshop support app (page content is depending on your one creativity)

The webshop side of the scenario without the shop :

(more…)

Vacatures bij AMIS services

Push-based synchronized slideshow web application – implemented using WebSockets and jWebSocket server – the open source Java WebSocket server

2
1 year ago
by Lucas Jellema in ,

In a recent article, I have introduced jWebSocket – an open source Java based server for WebSocket communication: http://technology.amis.nl/blog/14940/first-steps-with-jwebsocket-open-source-java-framework-for-websockets-installation-and-running-samples. In this article, I have described how to download and install the jWebSocket server and how to get going with running some of the distributed samples.

In another recent article, I looked at the implementation of a slideshow application where multiple web clients are mutually synchronized using WebSocket based communication using the Kaazing commercial Web Socket Gateway: http://technology.amis.nl/blog/14777/push-based-synchronized-slideshow-web-application-implemented-using-websockets-and-kaazing-websocket-gateway.

In this article, I will implement that same Slideshow application as with Kaazing, this time using the jWebSocket server as my underlying WebSocket infrastructure. It turns out that no server side configuration is required for this initial, somewhat naive implementation that does not use a specific channel but simply has all clients of the jWebSocket server participate in the communication. A more advanced set up would More >

Vacatures bij AMIS services

First steps with jWebSocket – open source Java framework for WebSockets – installation and running samples

6
1 year ago
by Lucas Jellema in , ,

This month, In have been delving into Push architectures for the Web, looking into WebSockets among several other things. WebSockets, a fairly new standard (!) evolved along with HTML 5, specifies a communication protocol that provides an alternative to classic HTTP communication. WebSocket based interaction has lower overhead and – more importantly – is bi-directional which means that push from server to client is really supported (and not just emulated through poll, long poll or streaming responses as is currently the case in comet push style frameworks).

All modern browsers provide support for the WebSocket specification – meaning they can communicate based on the WebSocket protocol (ws:// and wss:// in addition to http:// and https://) and they implement the WebSocket client side (JavaScript) APIs. These API are well defined – http://dev.w3.org/html5/websockets/ – and seem to be truly standard across all browsers.

The WebSocket server side is at this moment not very well defined. Other than the fact that the communication over ws:// and wss:// should be handled by a server, not much has been decided about the server side of WebSockets. Currently, WebSockets is not supported in More >

Vacatures bij AMIS services

Get going with Kaazing WebSocket Gateway – HTML5 Edition – installing locally and running demos

2
1 year ago
by Lucas Jellema in , ,

My last few articles on this blog site have all dealt with push architecture and technology in some way. This is an area that I have been investigating into quite bit recently. Part of these investigations had to be of course Kaazing, a specialized commercial offering, specifcally around WebSockets and its application in new HTML 5 application architectures.

Kaazing suggests a new way of implementing multi-tier (web) applications.

Communication between client and back end services happens over WebSockets. The Kaazing Gateway handles all WebSockets communication, turning messages from various back end services based on technologies such RSS, XMPP, JMS into WebSocket events.

Kaazing supports a variety of clients – though HTML 5 (JavaScript) web clients (including those running on mobile devices) are probably the most prominent ones.

(more…)

Vacatures bij AMIS services

Push-based synchronized slideshow web application – implemented using WebSockets and Kaazing WebSocket Gateway

9
1 year ago
by Lucas Jellema in , , ,

In the last few articles, I have discussed downloading, installing and running demos for a number of different tools, frameworks and libraries that support push-style (web) applications in one way or another. I have looked into ‘classic’ comet with Grizzly, Atmosphere and CometD as well as ADF Active Data Service and WebLogic Pub/Sub (Bayeux) Channels. I have also looked to WebSockets with jWebSocket, again Atmosphere and CometD and also with Kaazing. I intend to now take a closer look at some of these frameworks, by taking a simple push-style application and implementing it using each of these frameworks. The functionality I will be implementing is simple:

  • through the web client (HTML 5/javaScript), a user can select an image from a list of ‘slides’

  • the selection of the image is communicated to the server (background WebSocket based or alternatively regular AJAX)Comet (Bayeux)/Long Poll style)
  • the server informs all connected clients about the selected image through a pushed message (background WebSocket based or alternatively Comet (Bayeux)/Long Poll style); these clients all synchronize that slide selection
  • a Java (server side) component can also connect to the More >
Go to Top