[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orion-dev] Hashbang discussion
|
Am 11.02.2011 23:39, schrieb Boris Bokowski:
> http://server/coding.html#/path/to/file1.js
> ...
> So it's just a point in time where this URL format seems to be the most
> convenient for our development.
Right ;-)
I dislike this format. I remember reading on the wiki that Orion wants
to play nice on the web, including references to REST. I would prefer a
true REST format like <path>/<file>?task=xyz&anything=else.
Having "coding.html" in the URL seems like an implementation detail
leaking out.
What about other representations, in the REST sense? E.g. when I have an
file like onlinehelp.html, I would like to be able to use different
editors for it: task=editSource or task=editWysiwig or task=displayHtml,
the first or the last maybe being my default.
Another aspect is the WebDAV support that I noticed on the roadmap wiki
page. For WebDAV you would need to have RESTful URLs anyway. Then why
not make them the standard URLs?
Maybe you can cange the public URLs and keep another (secret) URL space
for the self-hosting Orion developers only to keep the fast edit-refresh
cycle.
Frank.
