atomic-server

atomic-server copied to clipboard

Atomic Classes can be used to generate Javascript / Typesript artifacts that help developers interact with instances of classes. As a JS dev, I want the following when working in...

joepio

[See docs issue](https://github.com/atomicdata-dev/atomic-data-docs/issues/113) Creating an Agent is too hard, it requires the Client to find an Invite resource, which is very different from creating a Commit. Also, the client does...

joepio

See https://github.com/atomicdata-dev/atomic-data-docs/issues/114

joepio

- Start atomic-server on `localhost` - Start again, on some other domain - Search for `string`, see two `/path` endpoint resources This happens because the `Db.populate()` command is ran twice...

joepio

Cache invalidation policy / logic for external resources

3

Atomic-Server caches external resources indefinitely, at the moment. This means that any Property or Class that exists somewhere else, may get out of date. That especially may become problematic when...

joepio

Example API: how to use Atomic Server from Node JS

3

I think it shall be quite easy to publish examples of how to use Atomic Data from Node to drive adoption (or validation of approach).

AlexMikhalev

Relates to #73 I'm trying to make the architecture of Atomic-Server as modular as possible, and basically dog-feeding a future Plugin interface. This interface should allow other developers to add...

joepio

Now that we have Files #107, users are likely to upload and use images. Very important here is the ability to resize (and often crop) images to keep websites performant....

joepio

Authorization checks are one of the largest performance costs at this time for Atomic-Server. The performance is still really good, but I'm sure we can speed up many requests by...

joepio

The `url::Url::parse()` function seems to be extremely slow. Find the bug, or get rid of the library. Maybe switch to this one: https://github.com/yescallop/fluent-uri-rs Edit: most of this was due to...

joepio