markuswustenberg / jsense Goto Github PK

Current design doesn't reflect actual usage, where setting the OutputStream effectively flushes.

Create a stream design instead, where events are added iteratively (maybe multiples) and flushed at will or when the underlying implementation thinks it should.

• Create sample based sliding window
• Overlap option

From Effective Java.

See http://central.sonatype.org/pages/ossrh-guide.html

See tcawley/gradle-protobuf-plugin@769c082 for config parameters

• Sign everything in the packages
• Check for replies: http://forums.gradle.org/gradle/topics/how_to_publish_artifacts_signatures_asc_files_using_maven_publish_plugin
• Make dependencies compile-time in POM
• Comment on ticket when first staging release is available: https://issues.sonatype.org/browse/OSSRH-9222

https://code.google.com/p/guava-libraries/wiki/IOExplained

What are the advantages to this?

http://code.google.com/p/mockito/

Currently, it's both returned and skipped, which might not work well for stream-backed data.

See http://yennicktrevels.com/blog/2013/10/11/automated-gradle-project-deployment-to-sonatype-oss-repository/

Using ByteSink/ByteSource and CharSink/CharSource.

Basically, comma-separated values or something like that.

For serialisation, perhaps?

The living tutorial.

Try deserializing events, first one with a relative timestamp present, the other one not. I think the timestamp will carry over.

So it's not duplicated.

Currently, they're being built manually, and the generated source added to the source folder. This is bad practice.

• Check that flush() calls underlying stream
• Check that close() calls underlying stream

Probably use Mockito here.

Figure out what to do with Iterators and IOException, because what's currently there isn't working.

Currently have to use an XML file, which seems unneccesary.

See http://www.gradle.org/docs/1.10/dsl/org.gradle.api.plugins.quality.FindBugsExtension.html and http://stackoverflow.com/questions/22037499/using-excludes-config-in-findbugs-and-checkstyle-plugin-in-gradle

• Robust, tested, lean, clean, nice code
• Separated for low dependencies
• Probably some of the same as in Guava
• Immutability (for concurrency)
• Works online, minimum amount of loading into memory
• Common data format for ubicomp community?
• Make the tasks uses often really easy

Might include:

• Timestamp of creation
• Comments
• Names

To PB, JSON, etc.