Skip to content
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.

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

two different resumptionTokens? #21

Open
ACz-UniBi opened this issue May 17, 2021 · 1 comment
Open

two different resumptionTokens? #21

ACz-UniBi opened this issue May 17, 2021 · 1 comment

Comments

@ACz-UniBi
Copy link
Contributor

Dear,

I notice that in the result xml's were two different resumption tokens:

...</record><resumptionToken completeListSize="56" cursor="" expirationDate=""></resumptionToken></ListRecords><ListSets><resumptionToken completeListSize="" cursor="" expirationDate=""></resumptionToken></ListSets></Response>

  • one under ListRecords element and
  • an empty one in ListSets

It seems, that the empty one under ListSets was added by 'metha-sync' and not in the repository response.

Observe anyone else similar?

Best, Andreas

@miku
Copy link
Owner

miku commented Oct 4, 2021

This is an effect of the implementation, which currently wraps any response type into a single struct. It has not caused too much problems in the past, although I admit, that it could be implemented in a better way. I think the thinking behind the single struct was to just a have a single response type.

I leave this issue open as a refactoring reminder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants