----- "Brice Figureau" <[email protected]> wrote:
> > > * Do you have any comments or concerns on the basic idea? > > I really like the idea. I've always be a proponent user of queueing > systems. > > I'm more reluctant about having the end clients connecting to the > queueing system directly. REST/HTTP is imho preferrable over Stomp > over SSL (ie I see a potential problem of client trust, or at least setup > complexity regarding SSL). Also it might be easier to firewall HTTP > than Stomp (excuse my complete ignorance about stomp here). It's just a TCP connection initiated by the client, just like http. Why do you consider REST preferable? We were talking about this last night and I don't really see the advantage, we'd still have a REST server option for smaller clients but I think for a big setup just avoid the HTTP. We didn't yet consider security in these requests which you get for cheap in HTTPS so we'd need to do a fair bit of additional work in the actual requests if we abandon http here. On the other hand some tools like ActiveMQ have built in REST, Websockets, AJAX and XMPP interfaces to the same queueing system which might help make the puppet code a lot simpler. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
