[orion-dev] Fw: Client side integration options

[Boris Bokowski <Boris_Bokowski@xxxxxxxxxx>]

oops, still trying to re-train my hand to click Reply All instead of just Reply...

----- Forwarded by Boris Bokowski/Ottawa/IBM on 2011/01/19 12:46 -----

From:	Boris Bokowski/Ottawa/IBM
To:	johnjbarton@xxxxxxxxxxxxxxx
Date:	2011/01/19 12:45
Subject:	Re: [orion-dev] Client side integration options

---

> Ok a variation:
> 
> If Firebug sees an http header
> x-edit-token:
> it will string trim it an issue
> http://localhost:8080/findFile?editToken=<opaque>&
> The server can use a URL encoded file URL for the token if it likes, or 
> it can hash the name if the security folks are watching.
> 
> Else if Firebug thinks it knows the local file, it issues
> http://localhost:8080/findFile?localFile=<encodedFileURL>&
> 
> In all cases the server redirects to the code.html URL (or whatever you 
> like).

How about this instead:

If Firebug sees an HTTP header
x-edit-url:
it will issue that URL to edit. The server can return any URL (including from other servers).

This would make it possible to have a site served from a different server (e.g., boris-test.orion-sites.eclipse.org) than the editor (e.g., orion.eclipse.org).

Why were you suggesting a token plus a rule how to turn that into a URL, instead of just a URL?

> Well I can do the remapping thingy now and if you want to try the 
> findFile thing let me know.

I can add the x-edit-* header this week, but we should agree on token vs. URL first ;-)

Boris