New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DeltaHandler: Unclear handling with ETags #225

Open

oli-h opened this issue Jun 13, 2018 · 0 comments

Contributor

oli-h commented Jun 13, 2018

Gateleen's DeltaHandler seems to have to main operation modes:

Work with a sequence number, automatically increased with each PUT, to find resources which are 'newer' than those a client already has
Work with ETag

Mode 1 is quite clear and well documented.
But behavior of Mode 2 - especially when combined with ExpansionHandler - is unclear:

It is not documented
It's not clear how and what a client should request (set which headers and/or parameters) to make use of the "Delta"-mechanism
Its magical how this mechanism can find resources 'which a client doesn't already has' - as we request only with max. one ETag (if-none-match or so....)

Need at least clarification and examples - or perhaps we find that the ETag based Delta-mechanism is broken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment