Unite is not Sucky Apache

Apache runs CGI scripts that do HTTP GETs, and those GETs don’t have the same power as clients that Opera does. For example, if a PHP script fetches a remote web page, it can’t execute Javascript that it finds. But that doesn’t mean it’s dumb for PHP to be able to do fetches, it just means that fetches have a different purpose in that context.

I bring this up to defend Opera Unite from what I see as unfair charges that it’s bad at file sharing, because I think it’s not designed for file sharing.

What is it? An incredibly potent extension to the toolkit of web apps, allowing them to do hacks which were fundamentally impossible in the past. For example, they could do interframe communications using RESTful interactions, by bouncing them off a local server. And they can receive asynchronous notifications! That’s a big deal.

Of course Opera Unite is sucky at doing the kinds of things that traditional web servers and file sharing tools excel at: it’s running inside a web page. Nothing you or the Opera people could do to fortify it would change the basic deal that it’s a daemon in a highly unstable operating environment. Uploading big files doesn’t make a lot of sense if the page the server is in is likely to disappear at any moment. On the other hand, uploading little things like RSS files and CVS diffs can pack a big punch.

3 thoughts on “Unite is not Sucky Apache

  1. My understanding is that each app is contained in a sandbox… do you mean that a single Unite instance could simply talk to the other sandboxes over HTTP — as though they were just web services on the web, but happen to be served from the local filesystem? Indeed, that IS interesting…!

    I just wish they'd pushed forward some of the discovery technologies (XRD/XRDS-Simple) that we've been working on!

Leave a Reply

Your email address will not be published. Required fields are marked *