David Pate

Thanks for the workaround @futpib that definitely addresses the issue. Also, you can change the encoding to something that `superagent` can handle such as `gzip` instead of `identity` as well.

Yeah, there definitely starts to be some interesting edge cases that we are running into as we continue to scale up. I'll see what I can come up with to...

Sure thing, @garemoko I'll take a look at the work that has already been done in the `1.0.3` branch and expand on it with some examples/clarification where possible. It's kind...

I'm 👎 on this, as what we are doing is correct currently. Currently we return no response body and a `204 (No Content)`, additionally an LRS is supposed to be...

Yeah, this is something that I think should be allowed no matter which piece you're querying for. The way that we allow it is to go through and have the...

There's definitely some interesting security issues that come up with needing to support arrays (no matter the implementation) for these types of things. For example, I could attempt to crash/DoS...

I don't agree with this at all as it no longer ensures that the LRS has a complete set of statements. It makes assumptions about the context of the statements...

You're making an assumption here that statements are only voided when they "contain errors" but that isn't the only use of a voiding a statement.

Yeah, it's definitely one use but if this is a truly interoperable system then each of the systems will work similarly (hence the specification). Have some LRS's which remove Voided...

With the current specification and retention of statements you could fully replay the entire history of the xAPI statements since none _should_ be removed from the LRS. So yes, as...