The obvious ones are VNC and GNU Screen, but the fundamental problem with these is that the client is too dumb and can't adapt to different form factors. The client needs to talk to the server in much higher level, more abstract terms.
This is where REST comes in. If you can sync URIs between devices, then REpresentations of application States can be Transferred to and from each device, and you should be able to seamlessly move sessions around, in theory.
In practice, not all web apps are properly RESTful and so won't work this way, though the landscape is certainly improving in this regard.
Also, not all apps are web apps, nor should they be. But a URI doesn't have to be a web page. I believe, and correct me if I'm wrong, that Android provides some sort of facility for native applications to intercept and handle arbitrary URIs. This could be used, for example, by a native Twitter client to show the equivalent native interface for a URI on the Twitter site.
Comments
This exists already, in a few different forms.
The obvious ones are VNC and GNU Screen, but the fundamental problem with these is that the client is too dumb and can't adapt to different form factors. The client needs to talk to the server in much higher level, more abstract terms.
This is where REST comes in. If you can sync URIs between devices, then REpresentations of application States can be Transferred to and from each device, and you should be able to seamlessly move sessions around, in theory.
In practice, not all web apps are properly RESTful and so won't work this way, though the landscape is certainly improving in this regard.
Also, not all apps are web apps, nor should they be. But a URI doesn't have to be a web page. I believe, and correct me if I'm wrong, that Android provides some sort of facility for native applications to intercept and handle arbitrary URIs. This could be used, for example, by a native Twitter client to show the equivalent native interface for a URI on the Twitter site.