- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 14 Apr 2019 19:27:39 +0000
- To: public-hydra-logs@w3.org
Entry point's URL also can change - with hydra the only stable URL would be an API Documentation's URL that should be provided by hydra powered API in each response's header. API documentation should provide an entry point. That's why it is possible to start with any URL. As for the sitemap like solution - I believe API documentation is the closest one - it's the place where client could obtain some details about the API on an ad-hoc manner. Still, it is up to the server on what's inside. Regarding the state - it's up to the client. Server just serves resources. That's why modern browsers are quite stuffed with features related to state storage (local storage, etc.) niedz., 14 kwi 2019 o 20:44 Jánszky László Lajos <notifications@github.com> napisał(a): > @tpluscode <https://github.com/tpluscode> I thought you always have to > start from the entry point, because the URIs can change. So if you save an > URI, then it can break later. I'd rather save the id and get the actual URI > template for it from the API. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/HydraCG/Specifications/issues/189#issuecomment-483038542>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AHvHNUbV8lBVya8iyl_dc-eWJ8SdlIyhks5vg3cpgaJpZM4cuaDO> > . > -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/189#issuecomment-483046241 using your GitHub account
Received on Sunday, 14 April 2019 19:27:41 UTC