On 10/23/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
>
>
> Hi Xavier,
>
> thanks for your reply - well yes, that's certainly right. I've just lost
> sight of it. But I got another question: how stable is the
> wicketstuff-push
> project or what sections are stable and which have to be improved for use
> in
> a professional webapp?
AFAIK wicketstuff-push is developed by vincent demay and myself. Vincent
worked on the cometd channel implementation, and I've worked mostly on the
timer based IPushService implementation (where events do not come from the
client at all). I don't know how stable is the channel implementation since
I don't use it myself, maybe Vincent could give more details (not sure if
it's used in production or not). For the IPushService implementation, it
still requires more testing and improvements, because the problem is not
easy to solve with a timer based polling implementation: we have to detect
clients disconnection, and also handle back button where pages go back to
life from the a serialized form. And we also need to work on a comet based
implementation of this push service. So I think there's still need for
improvement and bug fixing in this section.
BTW, I've just checked in an improvement about this problem of page
deserialization which required an API change for the IPushService. If you
plan to use it, do not forget to do an svn update.
Xavier
thanks in advance
>
> Michael
>
> Xavier Hanin wrote:
> >
> > On 10/22/07, Michael Sparer <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >> Hi,
> >>
> >> today I wondered if there's a wicket-approach for pushing messages from
> >> the
> >> server to the client (also called reverse ajax or pushlets). Well yes,
> >> there
> >> is one called wicketstuff push. I looked at its examples and soon
> managed
> >> to
> >> implement my own pushing stuff. In the examples (chat-example) however,
> >> the
> >> ChannelService that delivers the messages to its listeners, is stored
> in
> >> the
> >> application. I.e. there is only one channel for the whole application.
> >> Now imagine I want to create an additional private-chat-room for two
> >> users
> >> --> I'd need a ChannelService only for two users. So my question is:
> >> what's
> >> the wicket way to pass and store such an object which is applicable
> only
> >> for
> >> two users (sessions)?
> >
> >
> > You can use an application wide ChannelService and use the channel name
> > ("chat/message" in the example) to isolate messages by
> private-chat-room.
> >
> > Xavier
> >
> > Thanks in advance
> >>
> >> Michael
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13345278
> >> Sent from the Wicket - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://ant.apache.org/ivy/
> > http://www.xoocode.org/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/wicketstuff-push-and-sharing-an-IChannelService-tf4671463.html#a13358479
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
