Migrating from jquery-stream.1.1.2 to Portal

12 views
Skip to first unread message

Chen Harel

unread,
Jun 26, 2014, 8:21:21 AM6/26/14
to portal_...@googlegroups.com
Hi, I'm currently using jquery-stream.1.1.2 with my own AsyncServlet long polling solution based on tomcat 7 (java 6).
Sadly, it appears that recent versions of FF (29+ at least) broke support for this long polling and now only Chrome and Safari works.

I understand that jquery-stream is no longer supported and wish to migrate to Portal but haven't seen any migration guide.
I don't care (for now) about WebSockets support since I'm using the long polling as a push mechanism and for now that enough.

How do you recommend I proceed migrating to Portal?

P.s. from the documentation on Portal it seems the last version of FF is 12 which is obviously not the case.
Does it work for FF 30?

Chen Harel

unread,
Jun 26, 2014, 8:21:49 AM6/26/14
to portal_...@googlegroups.com
I meant jquery-stream 1.2. sorry

Donghwan Kim

unread,
Jun 26, 2014, 8:39:36 AM6/26/14
to portal_...@googlegroups.com
Hi Chen,

See inlines:

On Thu, Jun 26, 2014 at 9:21 PM, Chen Harel <chook...@gmail.com> wrote:
Hi, I'm currently using jquery-stream.1.1.2 with my own AsyncServlet long polling solution based on tomcat 7 (java 6).
Sadly, it appears that recent versions of FF (29+ at least) broke support for this long polling and now only Chrome and Safari works.
jquery-stream doesn't support long polling. Maybe misunderstanding somewhere?

I understand that jquery-stream is no longer supported and wish to migrate to Portal but haven't seen any migration guide.
I don't care (for now) about WebSockets support since I'm using the long polling as a push mechanism and for now that enough.

How do you recommend I proceed migrating to Portal?
There is no migration guide since migration from jquery-stream means rewriting app entirely.

Otherwise you can use Portal for Java.


P.s. from the documentation on Portal it seems the last version of FF is 12 which is obviously not the case.
Does it work for FF 30?
Not sure about what you are saying. Can you elaborate?

-- Donghwan

--
You received this message because you are subscribed to the Google Groups "Portal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to portal_projec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Chen Harel

unread,
Jun 26, 2014, 9:37:04 AM6/26/14
to portal_...@googlegroups.com
hi 
thanks for the quick reply! wow!

Regarding FF 30 and my problem. I believe it was due to a recent addition of compression of text/plain on our backend.
Chrome and Safari were ok with parsing "long polling" with gzip but FF was not.
Removing gzip from text/plain made it work again.

I am using jquery-streams with AsyncContext Servlet 3 (Tomcat 7). It is very similar to the ideas presented here: http://java.dzone.com/articles/non-blocking-nio-server-push

How do you call the type of mechanism used by query-streams in this manner if not long-polling?

Donghwan Kim

unread,
Jun 26, 2014, 10:06:31 AM6/26/14
to portal_...@googlegroups.com
You're welcome. Using 'chunked' with 'gzip' may conflict or depend client. But I'm not sure.

A way to establish a persistent connection over HTTP used in jquery-straem is HTTP streaming as the name suggests. :) If you are interested, see this section.

If you are satisfied with current situation, you don't need to migrate to Portal.

-- Donghwan
Reply all
Reply to author
Forward
0 new messages