We won't change API, user will continue to use service's name to manage it.
Some kind of service id will be used internally, this allow us to distinguish services with the same name, but different version. On Thu, Aug 9, 2018 at 4:32 PM Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > On Thu, Aug 9, 2018 at 4:41 AM, Vyacheslav Daradur <daradu...@gmail.com> > wrote: > > > Hi, Igniters! > > > > I found a ticket about a service’s versioning [1]. > > > > It’s out of scope IEP-17, but if we are going to implement this > > feature we should build a base in the first iteration of IEP-17 > > because of change messages formats. > > > > In case of the versioning which assumes that we are able to host > > services with the same name, but with different class/version, we > > should introduce *service’s id* to manage service’s lifecycle instead > > of service’s name. > > > > Thoughts? > > > > My only concern would be on the usability side. Is user going to have to > deal with IDs now, or will it be handled internally? > > D. -- Best Regards, Vyacheslav D.
