It implies more. Several web APIs uses the origin. For example IndexedDB,
XMLHttpRequest, WebSocket...
In this context it seems like same-origin should be generally non
problematic, assuming you can/want to trust activities... One might decide
to upload data for all the other activities somewhere
On 15 November 2013 00:39, Daniel Narvaez wrote:
>
> I wonder if we should first just fork sugar-web, implement the ideal API
> for Web/Android there and later figure out how reconcile with Linux.
> Reconciling is going to be a bit tricky I think, even more without a clear
> idea of what API we w
Let me understand this, when you talk about single-origin or
multiple-origin,
is only related to the LocalStorage access or imply something more?
Gonzalo
On Thu, Nov 14, 2013 at 7:50 PM, Daniel Narvaez wrote:
> Re server side. It would be necessary only with multi-origin. If you go
> with si
On 14 November 2013 10:03, Lionel Laské wrote:
> Here are the major issues I've faced building the prototype (all source
> code is here [2]):
>
>
>
>- Multiple copy of Sugar Framework in each activity. My work was
>mostly a way to group existing Sugar Web activities. BTW I need to upgrade
Re server side. It would be necessary only with multi-origin. If you go
with single-origin there is no point.
I'm honestly undecided between single and multi origin. I think multi
origin would be doing it right, but then I don't have a realistic way to
implement it that I'm really happy with. So..
Sure, but it's not a major concern. It's why we should edict some naming
rules eventually enforced by our own LocalStorage encapsulation in the
Sugar Web API that will prefix keys by the activity id.
Lionel.
2013/11/14 Manuel Quiñones
> 2013/11/14 Lionel Laské :
> >
> > My answe
2013/11/14 Lionel Laské :
>
> My answer is: we should go to simplicity.
>
> Regarding the one or many origin. I think, one is better. It allow sharing
> LocalStorage between activities which simplify a lot.
Imagine two activities that store a color in localStorage. If they
use the same key "color
My answer is: we should go to simplicity.
Regarding the one or many origin. I think, one is better. It allow sharing
LocalStorage between activities which simplify a lot.
Security is not an issue, I don't see any risk of hack here :-) We should
just indicate naming rules to avoid collision.
Regard
2013/11/14 Daniel Narvaez :
> Hi Manuel,
>
> current lack of standardization aside, there is another pretty fundamental
> security related issue here, that we probably need to make a conscious
> decision about.
>
> Those kind of API are usually associated to the web browser's web
> application fram
Hi Manuel,
current lack of standardization aside, there is another pretty fundamental
security related issue here, that we probably need to make a conscious
decision about.
Those kind of API are usually associated to the web browser's web
application frameworks, often requiring certain permission
Hi Daniel,
2013/11/14 Daniel Narvaez :
> I think there is a pretty fundamental issue we need to figure out, the
> solution to several of the issues you pointed out depends on this.
>
> Should activities be each a separate web application or should all the part
> of the Sugar web application? Or mo
Hi Martin,
2013/11/14 Martin Abente :
> Hola Lionel!
>
> AWESOME stuff you have there!
>
> Have you guys considered this [1] for collaboration?
>
> regards,
> tch
>
> Refs:
> 1. https://github.com/mozilla/togetherjs
C. Scott mentioned it, when it was under the name of "TowTruck". I
always wanted
2013/11/13 Lionel Laské :
>
> Hi Sugar lover,
>
>
>
> I must confess that like other here, recent discussions on this list don't
> inspired me a lot :-( Governance strategy or strategy of governance of the
> future of Sugar and SugarLabs is not my cup of tea. Worse: I'm afraid that
> this transpare
Sounds like you can have your own "custom" WebView in Phonegap, so it
should be possible one way or another.
On 14 November 2013 12:48, Daniel Narvaez wrote:
> It's probably possible on android WebView using a custom protocol with
> shouldInterceptRequest, I couldn't find anything about Phonega
It's probably possible on android WebView using a custom protocol with
shouldInterceptRequest, I couldn't find anything about Phonegap though.
On 14 November 2013 12:44, Daniel Narvaez wrote:
> Btw it might not be possible to do multiple origins using PhoneGap (or
> Android even), unless you lo
Btw it might not be possible to do multiple origins using PhoneGap (or
Android even), unless you load from a remote server rather than from the
application content.
On 14 November 2013 12:24, Daniel Narvaez wrote:
> I think there is a pretty fundamental issue we need to figure out, the
> soluti
I think there is a pretty fundamental issue we need to figure out, the
solution to several of the issues you pointed out depends on this.
Should activities be each a separate web application or should all the part
of the Sugar web application? Or more technically, should they have the
same origin
Hi all,
Thanks a lot for your messages regarding my work. Very appreciate to see
enthusiasm here.
I'm opening a different thread to talk about technical issues.
Technically speaking my prototype is three things:
- A Sugar Web Activities that mimic the desktop. This "activity" use the
18 matches
Mail list logo
