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

Encoded File Type Header Field? #6

Open
william-silversmith opened this issue Oct 29, 2021 · 0 comments
Open

Encoded File Type Header Field? #6

william-silversmith opened this issue Oct 29, 2021 · 0 comments

Comments

@william-silversmith
Copy link
Collaborator

william-silversmith commented Oct 29, 2021

We could adapt mapbuffer to add a content type header field. For example:

content_type char(5) = 'draco'

This would allow for automatic decoder selection. On the other hand, we could allow for arbitrary compression types and simply pass through unsupported ones. That would require only a code change and not a format change.

compression_type (4) = "drco"

However, the above change would be generally useful. For example gzip encoded json or xml could be represented.

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

1 participant