Closed andrewyatz closed 5 years ago
So far, the service-info endpoint is associated with an URL or subdomain like beacon.myserver.com/service-info or myserver.com/beacon/service-info
Thus, my initial guess was that no collision would happen on servers hosting multiple APIs.
If the above does not match the use case, we can go for the REST apprpach of:
Myserver.com/services > returning a list of service-infos
Myserver.com/services/{service id}/ > returning an specific service-infos
Makes sense?
Jordi
From: Andrew Yates [mailto:notifications@github.com] Sent: Wednesday, 1 May, 2019 12:02 To: ga4gh-discovery/service-info service-info@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [ga4gh-discovery/service-info] Service info for implementations which support multiple APIs (#22)
Brian from Cloud raised the idea that we could have a server, which implements multiple APIs. How can we support this idea? Feedback from cloud would be good as would anyone else.
Also cloud will go with a number of upcoming version changes with WES, DRS and TRS so it's a good time to get this scheduled in.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ga4gh-discovery/service-info/issues/22 , or mute the thread https://github.com/notifications/unsubscribe-auth/AB5SEOUQRCO3Y23SCPPPKODPTFTBJANCNFSM4HJSVVJQ . https://github.com/notifications/beacon/AB5SEOTXFJ7TWBMNYOPHFFDPTFTBJA5CNFSM4HJSVVJ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GRMNNGQ.gif
Miro suggested that this is in fact what the discovery service would do and the solution might be to get the discovery service defined. So it’s not a service info question
On Fri, 3 May 2019 at 20:06, jrambla notifications@github.com wrote:
So far, the service-info endpoint is associated with an URL or subdomain like beacon.myserver.com/service-info or myserver.com/beacon/service-info
Thus, my initial guess was that no collision would happen on servers hosting multiple APIs.
If the above does not match the use case, we can go for the REST apprpach of:
Myserver.com/services > returning a list of service-infos
Myserver.com/services/{service id}/ > returning an specific service-infos
Makes sense?
Jordi
From: Andrew Yates [mailto:notifications@github.com] Sent: Wednesday, 1 May, 2019 12:02 To: ga4gh-discovery/service-info service-info@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [ga4gh-discovery/service-info] Service info for implementations which support multiple APIs (#22)
Brian from Cloud raised the idea that we could have a server, which implements multiple APIs. How can we support this idea? Feedback from cloud would be good as would anyone else.
Also cloud will go with a number of upcoming version changes with WES, DRS and TRS so it's a good time to get this scheduled in.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/ga4gh-discovery/service-info/issues/22> , or mute the thread < https://github.com/notifications/unsubscribe-auth/AB5SEOUQRCO3Y23SCPPPKODPTFTBJANCNFSM4HJSVVJQ> . < https://github.com/notifications/beacon/AB5SEOTXFJ7TWBMNYOPHFFDPTFTBJA5CNFSM4HJSVVJ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GRMNNGQ.gif>
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ga4gh-discovery/service-info/issues/22#issuecomment-489206815, or mute the thread https://github.com/notifications/unsubscribe-auth/AABLSGOBH7Z4VTL2OUYNDFLPTSENDANCNFSM4HJSVVJQ .
We consider this to be out of scope and will be done by the discovery service. Confirmed on today's call
Brian from Cloud raised the idea that we could have a server, which implements multiple APIs. How can we support this idea? Feedback from cloud would be good as would anyone else.
Also cloud will go with a number of upcoming version changes with WES, DRS and TRS so it's a good time to get this scheduled in.