Sablier
Replies: 1 comment 2 replies
-
|
Hello @alx-xlx Blocking strategy is perfect for APIs, just as you did. And dynamic strategy is perfect for interactive UI, which is also what you did. You are doing this the correct way. If you don't think you are, can explain why ? Or why did you have any doubts ? Maybe I'll be able to clarify certain things for you. If my comment answers your question, please mark it as the answer. |
Beta Was this translation helpful? Give feedback.
-
|
I was just curious as in this way we have to use two different subdomains. one for blocking and one for dynamic. I mean I am also curious if there is any way to put some sort of loading ui mechnism on the blocking strategy that wouldn't interfere with the actual APIs if its accessed on the browser GUI. its all good, without it too. You have made an efficient project right here. |
Beta Was this translation helpful? Give feedback.
-
|
You could try to match the API on specific user-agent or something like that, maybe the path prefix for the api ? In that case you won't have multiple domains |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am running a Jellyfin container, and sometimes I visit jellyfin on webbrowser and sometimes on the native android or ios app like swiftfin etc.
I don't know which strategy to use is this case where I access the jellyfin in both ways.
So do I use two different subdomains ?
jellyfin.example.comusing the dynamic and the other subdomainjellyfin-api.example.comusing the blocking strategy ? Is this the correct way for my use case or can it be done better ?CaddyfileBeta Was this translation helpful? Give feedback.
All reactions