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

By: Yiannis

Yiannis — Wed, 01 Feb 2012 12:30:27 +0000

Hi there!
great tutorial! I have searched a lot but I have not found a tutorial with kaazing using an existing openfire server. Have you ever came across such a resource, or would you mind giving me some tips regarding this?
BR

By: Rolando Santamaria Maso

Rolando Santamaria Maso — Thu, 12 Jan 2012 15:43:46 +0000

Hi Lucas, nice example with Kaazing. Following your posts I can notice that you are making a websocket frameworks evaluation, wish is great, even better if you publish your conclusions.
Do you saw the jWebSocket slideshow demo?
Have funny with WebSockets

By: Push based synchronized Slideshow demo application implemented using CometD and jQuery running on Tomcat « AMIS Technology blog

Mon, 09 Jan 2012 10:59:14 +0000

[...] first article discussed the implementation using WebSockets and Kaazing Gateway (http://technology.amis.nl/blog/14777/push-based-synchronized-slideshow-web-application-implemented-u…). In this article, I will present an implementation using the CometD [...]

By: Lucas Jellema

Lucas Jellema — Sun, 08 Jan 2012 12:18:29 +0000

Hi Peter,

I have indeed used HTML 5 Edition. I was not trying to do anything ‘server side’ like in this case, so it seemed appropriate. I cannot give you a lot of other background. What would you say are criteria for choosing the edition to use?

I am still trying to work out how to integrate WebSocket communication – for example using Kaazing Gateway – with a traditional web application (Servlet/JSP or JSF based). Any suggestions in that direction.

greetings,
Lucas

By: Lucas Jellema

Lucas Jellema — Sun, 08 Jan 2012 12:14:19 +0000

Hi Quim,

I am afraid I have no experience with the PHP based server side. You may want to try ask on the Kaazing forum – or perhaps Peter Moskovits can chime in and help out?!

Licas

By: Lucas Jellema

Lucas Jellema — Sun, 08 Jan 2012 12:12:27 +0000

Hi Peter,

I think your question on the environment is answered by this article. I was wondering about the use of a single WebSocket connection. It must be my inexperience with Kaazing that made me do it this way. I do not know how to configure the Kaazing Gateway to work with a single channel that multiple clients can connect to – both browser based and Java client – and both publish to and consume from. If you could point me in the right direction, that would be very helpful. I too feel that a single connection should be enough!

Lucas

By: Quim

Quim — Sun, 08 Jan 2012 08:33:38 +0000

Very nice article.
Could you explain or reference how to do the server-side in php?
Â
Thanks,
Â

By: Peter Moskovits

Peter Moskovits — Sun, 08 Jan 2012 07:59:36 +0000

A few more questions: can you describe why you decided to use a listener and a sender? Since WebSockets are bi-directional, you may be able to come up with a solution that uses only one WebSocket connection.
Also – if you could share how you set up your environment (where the contents of the zip file needs to go in the kaazing gateway structure), that would be great!
Thanks!

By: Peter Moskovits

Peter Moskovits — Sun, 08 Jan 2012 07:29:02 +0000

Nice post, Lucas!
The Kaazing WebSocket Gateway comes is a number of flavors (HTML5, JMS, AMQP, etc.). It looks like you were using the HTML5 edition – can you confirm? Also, can you give some background why you chose the HTML5 edition?
I really like the idea of a slide-show tool: Â you can use it for real at conferences… very nice!