HTTP API V1

[stevensmedia]

Per a discussion on rhostdev:

Ashen-Shugar is toying with the idea of putting in a fully featured API and not just the header driven one. So you could http to the mush specify a dbref# like https://mysite.com/api/v1/dbref/123 .. then later drill down further with ~/attribute/nameofattr, or ~/flags or ~/toggles or ~/owner and so forth and depending on your credentials specifies if you can access that object and what you see on it. Andddd... the ability to edit and push values back anndddd... if the attribute is a $command have an 'execute' flag where you can specify arguments and have it optionally trace the output to you in the optional log window and the output in the output window. That's eventually where I'd like to go with the API but I can never get enough time.

Polk says "could support GET requests to recieve JSON bundles, POST to alter things, DELETE to trash an object..."
Ashen-Shugar says "Exactly"
Ashen-Shugar says "DELETE could delete attribute, flag, toggle, or an entire object"

Polk says "you could handle the ansi vs ascii stuff using the proper header for that"
Polk says "the accept header"
Polk says "could add something Accept: text/x-ansi"
Polk says "and default to text/plain"