Comments (4)
The above statement is probably intended to enable use of sticky sessions in a load-balanced environment
At the moment this is actually the case because some implementations do use sessions for caching expensive operations.
One example of this is when accessing a password protected shared element, in that case the element may be stored encrypted using bcrypt and when accessing the share using base64encode(shareId:sharePassword)
, verifying the password is expensive as it may be stored using bcrypt etc.
Sure. Could be solved otherwise on the implementers side so I'm just dropping my 2 cents here and explain why it was added on that document like that :-)
from ocm-api.
@LukasReschke Thanks for clarifying! I can understand this helps in tuning performance.
However, what you describe:
a) will probably apply for one specific implementation
b) should not be the client's concern
Therefore I think it should not be part of the generic specification. Apart from the discussion whether this should be included or not, (re-)sending cookies is generally not a standard practice for consuming APIs.
from ocm-api.
I agree wit you @joostfarla
I think very specific implementation details should be left out of the spec
from ocm-api.
Hi there, I'm trying to review what was left "To be discussed": this issue was taken into account some time in the past, as there's no more reference to such implementation details in the spec.
from ocm-api.
Related Issues (20)
- Activate GitHub Pages feature on this repo HOT 4
- [chore] Staging area for open PRs HOT 1
- NewShare field 'permission' is required but not defined HOT 1
- Document meshProvider field in NewShare HOT 3
- Endpoint discovery through https://example.com/ocm-provider/ HOT 4
- Group-owned shares and invites to/from groups HOT 3
- RFE: make invitation workflow symmetric HOT 1
- Cannot specify options per protocol in create share endpoint
- "protocol" or "protocols", which should implementers use? HOT 6
- Describe how "sharedSecret" may be used in WebDAV protocol HOT 3
- Do we want to support more than one protocol at a time? HOT 7
- Apply for funding to help develop Open Cloud Mesh within this community HOT 9
- Backwards compatibility HOT 5
- Document current translation that happens for webdav HOT 13
- support sub-shares? HOT 1
- Framing in terms of GNAP HOT 11
- Trade in shared secret for an OAuth-grade refresh/access token? HOT 4
- Security Considerations, from OSW session about RAP and comparing with CIBA-PUSH HOT 2
- Sequence Diagrams
- Why use refresh tokens? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ocm-api.