Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atmosphere 1.0.13 snapshot (2013-04-26) says, support Out Of Order Broadcast: false #1057

Closed
smithh032772 opened this issue Apr 30, 2013 · 5 comments

Comments

@smithh032772
Copy link

As I reported in the following forum thread,

PrimeFaces Push & 1.0.13 snapshot says, support Out Of Order Broadcast: false[1]

the following is showing up in the log:

Apr 30, 2013 11:21:02 AM org.atmosphere.cpr.DefaultBroadcaster
INFO: /administrator20130430112040 support Out Of Order Broadcast: false

If I revert to Atmosphere 1.0.13 snapshot (2013-04-15), then I don't see these lines in the log file.

Please fix this for the upcoming Atmosphere 1.0.13 release. Thanks.

[1] https://groups.google.com/forum/?fromgroups=#!topic/atmosphere-framework/PSaKjlFg8zk

@jfarcand
Copy link
Member

This is expected as noted on the ML. It has always been like that, e.g Out fo order == false.

@smithh032772
Copy link
Author

Okay, thanks. I'll continue to use 2013-04-15 version of atmosphere 1.0.13,
because that version does not does not output the INFO: ... to the log on
every user request. something has changed between 2013-04-15 and 2013-04-26
that causes the unwanted behavior in 2013-04-26 version.

On Tue, Apr 30, 2013 at 11:38 AM, Jeanfrancois Arcand <
notifications@github.com> wrote:

This is expected as noted on the ML. It has always been like that, e.g Out
fo order == false.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1057#issuecomment-17234942
.

@jfarcand
Copy link
Member

Why unwanted behavior? That just means you create a new Broadcaster :-)

@smithh032772
Copy link
Author

Hmmm... all this time, I've been dropping in new Atmosphere JARs, and have
never seen this behavior until I mix Atmosphere 1.0.13 snapshot
(2013-04-26) with TomEE 1.6.0 snapshot (2013-04-29).

Atmosphere 1.0.13 snapshot (2013-04-15) and TomEE 1.6.0 snapshot
(2013-04-29) do not result in this behavior. :)

On Tue, Apr 30, 2013 at 12:05 PM, Jeanfrancois Arcand <
notifications@github.com> wrote:

Why unwanted behavior? That just means you create a new Broadcaster :-)


Reply to this email directly or view it on GitHubhttps://github.com//issues/1057#issuecomment-17236612
.

@smithh032772
Copy link
Author

Jeanfrancois,

Click URL below, see the stacktrace, which is causing this log on every Full Page Refresh, and please advise. I see PrimeFaces Push and Atmosphere code more than anything else.

http://img40.imageshack.us/img40/4259/20130502atmospherelogon.png

thanks,
Howard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants