Skip to content

Documenting its behaviour better #120

@mkitti

Description

@mkitti

A good start is documenting its behaviour better - what is the buffer growth behaviour? How does one stop a transcoding? What is the "mark" in the buffer and how does one set and clear it?

I think documenting all supported behaviours is a good starting point for thinking about the API. For example, the way to stop a transcoding is to write a TOKEN_END to a stream. The obscurity of that suggests perhaps that should be a method instead

Metadata

Metadata

Assignees

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