Re: Soliciting feedback on a UX change for route services

Shannon Coen

On Wed, Jun 24, 2015 at 1:51 PM, Mike Youngstrom <youngm(a)> wrote:

I'm excited to eventually bind services to more CF entities like
services. Binding a service to a route is as good away as any to start
users thinking that services could be bound to more than just an app.

I'm not a fan of the proposed create-route/update-route cli syntax. Would
it be possible to bind more than one route service to a route with that
syntax? I'd prefer something like bind-route-service/unbind-route service
Initially we're targeting support for one service per route, and
create-route/update-route accomplishes this simply. Associating multiple
services with a route isn't as simple as binding an app as they are not
independent. An order of chaining would have to be declared. In any case,
I'll admit that update-route doesn't scale well beyond a single service.
It's worth considering a UX that doesn't prevent predictable feature

Join { to automatically receive all group messages.