A question about authentication
Matt Mower
From my reading of the spec & examination of the ruby stompserver is seems like authentication is, primarily, a server-connection matter.
In my use case we will have hundreds, hopefully thousands, and if we're super lucky, hundreds of thousands of topics and not all clients should be equally able to subscribe to them. So I'm looking for a way to have subscribing to & sending to topics require separate authentication.
Am I alone in this requirement? If not, how are people handling this?
Any help would be much appreciated, thanks.
Matt
/aside Referencing my other thread one of the reasons I picked the Ruby stompserver was that I might be able to hack in what support I need, myself
Hiram Chirino
Hiram Chirino
Software Fellow | FuseSource Corp.
chi...@fusesource.com | fusesource.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo
Matt Mower
On Jan 26, 4:25 pm, Hiram Chirino <hi...@hiramchirino.com> wrote:
> The Apollo STOMP sever has outstanding security. Here's a link to the
> security section in it's manual:
>
Apollo looks very capable and, if we're successful, I'm sure it's
exactly the kind of thing we'd want. But, at the same time we're a
tiny startup and I'm not sure I have time to figure out what appears
to be a complex piece of infrastructure. I liked Ruby stompserver
because it was trivial to deploy and run. That said it might be that
what time I have is better spent learning Apollo than modifying
something like Ruby stompserver.
Any other options?
Matt