You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[..] There is a scale issue as well. For example, we have a service that converts a pdf into units of thought which results in up to milions of triples per pdf. So it could be a big burden for a server to handle redirects etc for millions and millions of uris per moved user
A resource in our case is as small as a single triple, and there can be 100's of millions of these in a pod, so scale is an issue but I guess you really just need a pattern matching at the server level to do it. Such that any request with a certain uri pattern would redirect to another pattern.
This should either be discussed and addressed in the spec, or mention may need to be made if the spec is not otherwise adapted in this direction.
The text was updated successfully, but these errors were encountered:
As noted on Gitter by @gibsonf1 (thank you!)
This should either be discussed and addressed in the spec, or mention may need to be made if the spec is not otherwise adapted in this direction.
The text was updated successfully, but these errors were encountered: