Real-life use?

[algo]

Hello,

Anyone uses cometd in real production?

Particulary, I mean cometd-javascript.

[Simone Bordet]

Hi,

I know of big telco companies that are using it, potentially
targetting thousands/millions users.
Big sites that offer sport results and statistics, as well as game
sites using it to let the users play (again with a huge audience).

Why you're asking ?

Simon
--
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless. Victoria Livschitz

[Ilia Kantor]

Hi, Simone,

Thanks for answering.

2 years ago the cometd was very raw, I believe it matured a lot.
Good to know I can get to using it too now ;)


2009/11/6 Simone Bordet <simone...@gmail.com>:

[Dylan Schiemann]

Chess.com's live chess is another good example.

Good to see you around Ilia!

Regards,
-Dylan

[Ilia Kantor]

Is there any tutorial or kindof, how to implement authentication on
top of cometd ?

E.g how to create a chat?


2009/11/6 Dylan Schiemann <dyl...@gmail.com>:

[Simone Bordet]

Hi,

On Fri, Nov 6, 2009 at 20:18, Ilia Kantor <ili...@gmail.com> wrote:
>
> Is there any tutorial or kindof, how to implement authentication on
> top of cometd ?

No.
Can you please file a bug at http://bugs.cometd.org about that ?

> E.g how to create a chat?

You have the example demo shipped with cometd that shows a full chat
application.

[Luis Montes]

I understand that we can have clients publish to a /service channel and have a BayeuxService that only delivers to certain other clients.  We can do whatever type of authentication we wish there since we have a handle on the request.

Is it possible to stop clients from subscribing to a channel at all?

[Martin Hewitt]

I tend to have my clients authenticate away from the comet system(s),
through a vanilla servlet, then make the HttpRequest available to
comet, and use Java's built-in session to map a logged in,
authenticated, user to a cometd clientId, and then exchange tokens as
necessary to authenticate further push sessions.

I know there's a canHandshake method where one can implement
first-footfall authentication, to stop a client even connecting, but
it's never fit my use case, so I've tended towards the above.

Martin

2009/11/7 Luis Montes <mont...@gmail.com>:

[Simone Bordet]

Hi,

On Sat, Nov 7, 2009 at 01:31, Luis Montes <mont...@gmail.com> wrote:
> I understand that we can have clients publish to a /service channel and have
> a BayeuxService that only delivers to certain other clients.  We can do
> whatever type of authentication we wish there since we have a handle on the
> request.
>
> Is it possible to stop clients from subscribing to a channel at all?

Yes. You implement a custom SecurityPolicy, override canSubscribe()
and attach it to the Bayeux object.