24/7 sites (permanent applications - idea)
This is an advanced topic, this is not required to use or develop for Opera Unite.
To run the Opera Unite service non-stop, you could probably rent a cheap VPS, install Linux with X environment on it and run Opera on that server (you can run virtual desktop with VNC →).
This is pretty feasible.
The only concern here is performance, but that's something I'd have to test soon.
This article is a stub, it contains information that doesn't explain subject fully.
Last updated
- Markuper (HTML templates)
- .ua
- Opera Unite HowTo's
- .us (files)
- Distribute Your Application
- 24/7 sites (permanent applications - idea) [stub]
- Issues
- HTTP Connections (AJAX/REST)
- Cookies
- file_wrap.js - File Wrapper
- Basic HowTo: Simple app (tutorial)
- Static images, client-side scripts
- Application Examples
- How to Debug Opera Unite apps
- Persistence & databases
- Opera Unite benchmark
- From PHP to Opera Unite
- Uniteness (Framework)
- Config.xml
- Key-value storage
- Widget Object
- Notifications (Growl'esque)
- Reset (debug)
- Cron example
- What I meant by CNAMEs
- Wish List
- Device Unavailable
- StopLorem (Opera Unite blogging)
- uniteness-0.11
- GET/POST data
- CRUD And Static (example)
- Opera object
- URLs
- Headers & Redirects
- Error Console
- JSON State (storing data)
- Security
- /storage/ (in fileio)
- Yusef library
- unite_info (a-la php_info)
- Javascript Imports
- onunload / _close
- fileio: Sandboxed Filesystem
- Request Hierarchy (like php_info)
- Intro: Web Apps with Opera Unite