-
Notifications
You must be signed in to change notification settings - Fork 24
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
No such status as "object not available" #629
Comments
I sent #651 to fix this, but I'm not seeing any text that indicates we're sending EndOfGroup status. |
It's by implication. Object Does Not Exist is explicitly mentioned as something to omit, so by implication all other objects are included. the FETCH section could say "all non-normal objects are omitted" but it doesn't say that. |
Individual Comment: I was thinking end-of-group is useful for a fetch cache, so it can define the bounds of the group. I suppose omitting it and sending an object from a later group implicitly does the same thing though. |
It might be. I haven't thought about it deeply, but we should decide how this works with intent instead of accidentally specifying it in the way we have. |
In 6.7 FETCH it says
"All omitted objects have status Object Not Available."
This status doesn't exist. The closest status is "Object Does Not Exist"
I was surprised that we are sending EndOfGroup status, etc, but I can definitely live with that.
The text was updated successfully, but these errors were encountered: