jstuyts / elko Goto Github PK

Mods and encodables currently use a simple name in their global namespaces. This can easily lead to collisions when having to integrate mods or encodables from multiple parties.

Suggestion: Tag URI

The UTF-8 decoding in ChunkyByteArrayInputStream does not handle all code points. Use the standard decoding built into the JDK instead.

Also move the reading of character-based data out of the class, as it is an input stream and not a reader.

When a message cannot be parsed properly, the client or server starts consuming a lot of CPU.

The names are a bit misleading:

• Local: direct connection to a database implementation.
• Remote: connection to a repository server (which connects directly to a database implementation).

In The Unum Pattern, it is stated that:

Perhaps the server has revealed the secret message hidden in the teacup to my client (and to none of the others) because I possess a magic amulet that lets me see such things.

This implies that the server presence needs more information than that data needs to be sent to the client. But currently there is no way to provide or let the server presence determine additional information on which to base the data to be sent to a specific client.

Extend the presence serialization to allow for more complex policies about what a specific client needs or is allowed to see.

Note that it requires special handling (which seems to be broken because only code to save the position as _qpos can be found) by the MongoDB object store.

Do not use a global variable, that will require recompilation for changes, for determining whether or not to send debug replies.

When adding a mod, it is also registered by its super classes. If two mods inherit from the same base class, then only the last added mod will be retrievable by the super class.

Unums have presences, but there is also a presence server. These are different kinds of presences (unum representations/views and whether a user is online respectively), so it is better to use different terms to avoid confusion.

Suggestions for unum presences:

• Presunce
• Ubeity (very uncommon word, so likely not known by many people)

When attaching or detaching a mod, the object is not marked as changed, so when doCheckpoint(...) is invoked, the changes will not be saved.

If marking has to be added, should the marking only occur for non-ephemeral mods?