Skip to content

Clarify what it means for clients to support batch #177

Open
@DanielOaks

Description

@DanielOaks

It's pretty explicit when servers support batches. Q: Do they send batches. A: Y/N.

However, when it comes to clients... it's much less explicit. Some example questions we could apply:

  • Do they request the batch capability by default?
  • Internally, can they track which messages are part of which batches?
  • Can they post-process messages after they receive the 'batch end' message, collapsing them to display more nicely?
  • Do they correctly collapse one or more of the standard batch types, and handle them explicitly?

I dunno, it's hard to say when a client really supports 'batches'. What I think makes the most sense is for the actual batch column on the standard support page to be green when the client requests / can request batch (and handle messages in batches without dropping them or similar), and to create a similar batch-types support page similar to the SASL mechs support page, detailing exactly which batches are supported.

The above is what I'll be going by for the future, and I'll make that batch types support page sometime soon.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions