Diego Parrilla Santamaría writes:
> May be it's a bit too late, but in mid 2012 the FIWARE team developed a
> horizon clone 100% in Javascript. https://github.com/ging/horizon-js
Nice! I poked around a little in the repo and found no mention of Swift?
> [...] Portal has evolved and now it's mor
May be it's a bit too late, but in mid 2012 the FIWARE team developed a
horizon clone 100% in Javascript. https://github.com/ging/horizon-js
Sadly, CORS support was not even in roadmap for OpenStack, so the
horizon-js project was not valid for production at that time.
In StackOps we developed Por
Richard Jones writes:
Hi,
I'm working on the ZeroVM project at Rackspace and as part of that I'm
writing a JavaScript based file manager for Swift which I've called
Swift Browser:
https://github.com/zerovm/swift-browser
When writing this, I of course ran in to exactly the problems you
descri
On 12 September 2014 09:24, Richard Jones wrote:
> On 12 September 2014 07:50, Adam Young wrote:
>
>> So, lets have these two approaches work in parallel. THe proxy will get
>> things goint while we work out the CORS approach.
>>
>
> I will look at submitting my middleware for inclusion anyway
On 11 September 2014 18:00, Robert Collins
wrote:
> FWIW I'm very much in favour of having a single host API - I was
> looking at doing that in Apache for TripleO deployments anyway, due to
> the better SSL deployment characteristics. We then would register the
> actual single host endpoint in pu
On 12 September 2014 07:50, Adam Young wrote:
> On 09/11/2014 03:15 AM, Richard Jones wrote:
>
> [This is Horizon-related but affects every service in OpenStack, hence no
> filter in the subject]
>
> I would like for OpenStack to support browser-based Javascript API
> clients.
> Currently this
On 09/11/2014 03:15 AM, Richard Jones wrote:
[This is Horizon-related but affects every service in OpenStack, hence no
filter in the subject]
I would like for OpenStack to support browser-based Javascript API
clients.
Currently this is not possible because of cross-origin resource
blocking in
FWIW I'm very much in favour of having a single host API - I was
looking at doing that in Apache for TripleO deployments anyway, due to
the better SSL deployment characteristics. We then would register the
actual single host endpoint in publicURL.
How would that work for multiple regions with java
[This is Horizon-related but affects every service in OpenStack, hence no
filter in the subject]
I would like for OpenStack to support browser-based Javascript API clients.
Currently this is not possible because of cross-origin resource blocking in
Javascript clients - that is, given some Javascri
