search

AdaHeads / call-flow-control

Call-information flow server.
Other
6 stars 8 forks source link

Client configuration interface #5

Closed rostgaard closed 11 years ago

ThomasLocke commented 11 years ago

Done. A simple /configuration REST interface is now available. Right now it doesn't do a whole lot, besides hand out a JSON with a couple of url's added. Since we haven't fully decided what goes into the configuration interface and how to store it, I opted for a simple solution. For now it is very straightforward to add new key/value pairs to the configuration JSON.

rostgaard commented 11 years ago

I don't think URL's are a configuration parameter, excluding hostnames obviously.

See: https://github.com/AdaHeads/Bob/blob/master/web/js/Configuration.js for inspiration. Can we put the config in the same form as org documents? E.g. JSON in SQL. This way we can make a configuration local to the agent.

ThomasLocke commented 11 years ago

I'll add the notion of individual configuration objects when we actually have a user model and individual users in the database. It's trivial at that point, and I'd rather not waste time on it right now, seeing as the chances of me getting it right equals 0. This will all come to light when the OpenID stuff is added.

I've no issue with adding what is in the web/js/Configuration.js file, so consider that done.

For now be content with a local configuration.json.dist file in the configuration/ directory. Just get rid of the .dist part and you have your very own local configuration file. This also ensures that we can easily add/remove new keys and have individual developer configurations while things are in heavy flux.

rostgaard commented 11 years ago

Actually we do have an agent formalized https://github.com/AdaHeads/Alice/wiki/Schema%20Agent