|To main page | Opera Unite HowTo's|
There's a number of things I think Opera might consider implementing (that we, Third-Party Developers, just can't implement), so I'll just leave a list:
CNAMEsUPDATE: What I meant by CNAMEs
Although Opera might lose some advertising points, but I think a lot of people would rather put "Powered By OperaUnite" banner, rather than having to type "http://compute.your_opera_login.operaunite.com/application/" instead of "http://myapp.com/".
myapp.com be defined as CNAME → for
application.compute.your_opera_login.operaunite.com. // to particular app on deviceor
compute.your_opera_login.operaunite.com. // to deviceMost Registrars handle CNAMEs on their DNS servers transparently to user. I.e. - just pay 10$ and tell us where to point it.
"User-friendly" URLs"User-friendly" URLs would have been:
http://application.your_opera_login.operaunite.com/(Note the "application" instead of "mydevice", I think the devices should resolve "same app" URL conflict themselves, like if both devices have same app - second one gets "application_1").
Or at least:
http://application.mydevice.your_opera_login.operaunite.com/Then we won't have to use:
o.write('<img src="' + webserver.currentServicePath + 'imgs/a.jpg'..instead we could just write:
o.write('<img src="/imgs/a.jpg" '..