One year of io-tools.

7 views
Skip to first unread message

dvd.smnt

unread,
Jan 19, 2010, 5:27:05 PM1/19/10
to io-tools
Now it's heading to the 1.3 release and the code is much more stable
and mature than the first 1.1 one year ago. Anyway the two libraries
that makes the project are in a different development stage.

Easystream is a quite stable codebase. It is well documented, and it
is currently used in production environment by some companies. It's a
kind of library that once you integrate it you'll forget of it. Future
developments will include better documentation and improvements of the
`OutputStreams` api.

Wazformat has a completely different situation. Some serious bug are
still open, and a big performance improvement is needed. The good news
is that the api has a good design and doesn't need an huge rework.

* 70 formats are not a lot, many more formats should be supported.
Unfortunately the main detection library "Droid" is developing *VERY*
slowly and its performances are not suitable for production
environments. I admit it was not a good idea to use it. It's not just
the library, also the detection sequences used are not well designed.
They look for bytes at the end of the stream, forcing the library to
buffer it completely.
* There is no idea of format "subclassing". This should be brought
in.
* Also mimetype detection should be in future wazformat releases.

In future developments I will look to the S-MIME shared format
database (maybe through an enhancement of the native detection
strategy). I'm writing a project draft that should be in the wiki in
some weeks.
Any help in design/implementation/testing/documentation will be
welcome.

Many thanks to everybody who contributed reporting bugs and suggesting
enhanchments.

Davide.

Reply all
Reply to author
Forward
0 new messages