commit | 4ecdcbc119359ed4214405cdb6512f4445a7cc92 | [log] [tgz] |
---|---|---|
author | mfrancis107 <mfrancis107@gmail.com> | Wed Oct 18 12:07:30 2017 -0400 |
committer | Kevin Moore <kevmoo@users.noreply.github.com> | Wed Oct 18 09:07:30 2017 -0700 |
tree | 7d7fa03d61c138f6a0138b41d5e236b62d916853 | |
parent | 367087506c0a8a746bd75c685487b01ffed7f1c5 [diff] |
Adds support for glTF - text and binary formats (#9) See: https://github.com/KhronosGroup/glTF
#MIME type package
Package for working with MIME type definitions and for processing streams of MIME multipart media types.
##Determining the MIME type for a file
The MimeTypeResolver
class can be used to determine the MIME type of a file. It supports both using the extension of the file name and looking at magic bytes from the begining of the file.
There is a builtin instance of MimeTypeResolver
accessible through the top level function lookupMimeType
. This builtin instance has the most common file name extensions and magic bytes registered.
print(lookupMimeType('test.html')); // Will print text/html print(lookupMimeType('test', [0xFF, 0xD8])); // Will print image/jpeg print(lookupMimeType('test.html', [0xFF, 0xD8])); // Will print image/jpeg
You can build you own resolver by creating an instance of MimeTypeResolver
and adding file name extensions and magic bytes using addExtension
and addMagicNumber
.
##Processing MIME multipart media types
The class MimeMultipartTransformer
is used to process a Stream
of bytes encoded using a MIME multipart media types encoding. The transformer provides a new Stream
of MimeMultipart
objects each of which have the headers and the content of each part. The content of a part is provided as a stream of bytes.
Below is an example showing how to process an HTTP request and print the length of the content of each part.
// HTTP request with content type multipart/form-data. HttpRequest request = ...; // Determine the boundary form the content type header String boundary = request.headers.contentType.parameters['boundary']; // Process the body just calculating the length of each part. request.transform(new MimeMultipartTransformer(boundary)) .map((part) => part.fold(0, (p, d) => p + d)) .listen((length) => print('Part with length $length'));
Take a look at the HttpBodyHandler
in the http_server package for handling different content types in a HTTP request.
Please file feature requests and bugs at the issue tracker.