LinkAP

[Paul Frazee]

Hey all,

I've been working on a similar project for a while. Just came across Unhosted, so I thought I'd share.

http://linkapjs.com/

It's focused on the security and communication model for cooperative applications. Still fairly unproven, but I'm working on a deployment host and plan to start building apps at Hack TX this weekend.

Cheers,

Paul

[Melvin Carvalho]

Looks very interesting!

Quick question:  Could the postMessge wrapper be extended to send a message from one browser to another using lap:// ?
 

Cheers,

Paul

--
 
 
 

[Paul Frazee]

Quick question:  Could the postMessge wrapper be extended to send a message from one browser to another using lap:// ?

Yeah, I think so. Basically that's communicating across sessions, so you'd need a way to identify and reach it. In the Satellite server, I'm creating a unique resource for each session (http://sat-server.com/sessions/21412) so that you could proxy via that uri (lap://app.ui/some/resource via http://sat-server.com/sessions/21412). The satellite would then need a websocket connection to the active session, which could then serve the response. Or, once WebRTC hits, it might serve it P2P.

It's a bit complicated, but it should work.

[Michiel de Jong]

oh, cool! thanks for joining our list. yes, we're all about
client-side web apps and tearing down walls. :)

interesting that you don't use cross-origin ajax, but rather a sort of
cross-webworker ajax, is that right? so you have one page that's sort
of the host, and that manages apps inside webworkers? i'm think it
would really help to see it working in order to exactly understand how
it fits together, but it definitely sounds exciting! :)

cheers,
Michiel

> --
>
>
>

[Melvin Carvalho]

On 16 October 2012 18:40, Paul Frazee <pfr...@gmail.com> wrote:

Quick question:  Could the postMessge wrapper be extended to send a message from one browser to another using lap:// ?

Yeah, I think so. Basically that's communicating across sessions, so you'd need a way to identify and reach it. In the Satellite server, I'm creating a unique resource for each session (http://sat-server.com/sessions/21412) so that you could proxy via that uri (lap://app.ui/some/resource via http://sat-server.com/sessions/21412). The satellite would then need a websocket connection to the active session, which could then serve the response. Or, once WebRTC hits, it might serve it P2P.

It's a bit complicated, but it should work.

Awesome.

You might want to look at browserver

http://browserver.org/

Or Chrome's webserver

https://github.com/GoogleChrome/chrome-app-samples/tree/master/webserver
 
Unique resources seem to be a very good idea.

I need to look more at webRTC still! :)

On Tuesday, October 16, 2012 10:42:06 AM UTC-5, Melvin Carvalho wrote:

On 16 October 2012 16:53, Paul Frazee <pfr...@gmail.com> wrote:

Hey all,

I've been working on a similar project for a while. Just came across Unhosted, so I thought I'd share.

http://linkapjs.com/

It's focused on the security and communication model for cooperative applications. Still fairly unproven, but I'm working on a deployment host and plan to start building apps at Hack TX this weekend.

Looks very interesting!

Quick question:  Could the postMessge wrapper be extended to send a message from one browser to another using lap:// ?
 

Cheers,

Paul

--
 
 
 

--
 
 
 

[Paul Frazee]

@Michiel...

interesting that you don't use cross-origin ajax, but rather a sort of
cross-webworker ajax, is that right? so you have one page that's sort
of the host, and that manages apps inside webworkers?

Yep

 

i'm think it would really help to see it working in order to exactly understand how
it fits together

Yeah, that's what I'm after this weekend. I had some apps in earlier versions, but they fell out of compatability.

@Melvin: Chrome webserver would be huge if it became a standardized browser api. Maybe usable through plugins or something. Will keep that in mind, thanks.