Taro L. Saito

It's a very interesting topic and I think we basically need a staging data store and transaction protocol for supporting atomic commit. - First, API should provide write-only pre-signed URLs...

ok. I'll rebase this PR onto develop

It's been already rebased. @pjfanning

@Taig Thanks. Explicitly removing JS projects worked for me. But I guess sbt-unidoc is including projects not mentioned in `aggregate` when building scaladoc.

@sjrd Good to know that. Do you have any idea how we can expose node.js functionality at `jsEnv` even though jsdom is used? (rather, my question would be how it...

(Plan3) Catch all of the exception within `log` method, then return an Success or Failure object. Both objects define `boolean isSuccess()` and `boolean isFailure()` method, and when Failure provides last...

(Plan4) Returns true/false and when false, users retrieve `lastUnsentLogs` from the FluentLogger instance.

I continued the discussion with @komamitsu in Twitter. In his idea, handling checked exception with try and catch clause is cumbersome for the users. I agree with him in this...

Wow, Plan1 (Using an error handler) makes the user code simplest. The other options are a little bit intimidating to the users.

@komamitsu Right. if plan4 returns false, its cause can be buffer full, send error, message pack error, etc.