search

FDSN / SeedLink

https://docs.fdsn.org/projects/seedlink/
Creative Commons Zero v1.0 Universal
1 stars 1 forks source link

Question: GETCAPABILITIES vs INFO #14

Closed CharlesBlais closed 8 months ago

CharlesBlais commented 1 year ago

As part of https://seedlink.readthedocs.io/en/latest/protocol.html, it states:

GETCAPABILITIES returns space-separated server capabilities (Capabilities) as a single line terminated by .

INFO item [station_pattern [stream_pattern[.format_subformat_pattern]]] requests information about the server in JSON format

It seems GETCAPABILITIES and INFO could be used for the same purpose As the description states, both return information about the server. Should they maybe be merged?

Also, for INFO, would it help if the currently authenticated user name be part of the response? Much like “whoami” on Linux. That might help to determine "why am not seeing the station" because of the required AUTH command for certain stations.

crotwell commented 1 year ago

I agree, INFO CAPABILITIES seems like a more natural way to do this than a separate command.

And I think the response of GETCAPABILITIES is effectively also currently included in the response to HELLO. It is needed there so clients can determine which protocol version is supported.

The json schema would also need to be updated.

andres-h commented 1 year ago

Feedback from proposal team

Agreed on dropping GETCAPABILITIES.

Change of specification

Remove all references to GETCAPABILITIES.

crotwell commented 9 months ago

+1 on change