Hmm. I wonder whether Opera has macros -- I haven't noticed that feature, but I'd never gone looking for it until now either. A macro that fires off a rsh command would work when both the current and target machines are running Linux/Unix ...
... but I mostly only run Opera on one Linux box, plus three Windows machines and a Mac. That's something Windows boxes are good for: running web browsers and telnet clients (to get shells on all the Linux machines downstairs, of course). ;-) So this command being between two Linux machines will be an unusual case (in my house). There'll usually be Windows on one end or the other. Though I did wish I could bounce a web page from the bedroom Linux machine to the iMac, night before last.
Anyhow, I'm probably SOL regarding the Mac (until I get my hands on one that'll comfortably run OS X, anyhow (I'm currently running OS 8.6 and OS 9)), but I wonder what Windows has in the RPC department. And how it wants to handle authentication.
Argh. That reminds me that I'm having trouble getting Win98 to talk to my Samba server (which is also serving Appleshare and NFS, of course, because I never got around to installing and configuring the Andrew File System). The WinNT machine can connect. The Win95 machine could connect until it ate itself and got moved to the repair pile. The Win2K machine can connect. It's just Win98 that doesn't want to. And I could swear I've solved this problem before and should have notes about it somewhere, but damned if I can figure out where said notes would be.
*ponder* Ok, that makes things more difficult... But if Opera does have the macros feature that allows you to call CLI commands, and like Firehamster, has the "remote-control" feature that allows you to load things into a running instance, then you could implement your own somewhat-hacky version using something like "socket" (Interrobang and I found that "netcat" is at least available for Windows, if nothing else is). Or if that's no good in terms of security (don't think you can block what clients connect with netcat/socket), you could probably make a server using Perl.
Basic operation for the server would be, listen on some obscure port, lines read from the socket would be URLs to display; display them by running opera --whatevertheremotecontrolargumentis URL And then close the connection and go back to listening for connections. It'd probably be wise to add some sort of basic authentication though, like have the first line as a sanity check and the second line give a password or somesuch, and then only the *third* line be the URL for instance. And as some stupid sites insist on using whitespace in URLs (eg, Slashdot who should know better), you might want to escape the line you read before running the command. Perl can do that easily enough, but if using socket/netcat, you'd want to pass it through sed (yes that's IIRC available on Windows too) or something.
Hope this has given you some more ideas! Whether or not Opera is up to the task, Windows use shouldn't get in the way too much of getting such a thing done.
(no subject)
... but I mostly only run Opera on one Linux box, plus three Windows machines and a Mac. That's something Windows boxes are good for: running web browsers and telnet clients (to get shells on all the Linux machines downstairs, of course). ;-) So this command being between two Linux machines will be an unusual case (in my house). There'll usually be Windows on one end or the other. Though I did wish I could bounce a web page from the bedroom Linux machine to the iMac, night before last.
Anyhow, I'm probably SOL regarding the Mac (until I get my hands on one that'll comfortably run OS X, anyhow (I'm currently running OS 8.6 and OS 9)), but I wonder what Windows has in the RPC department. And how it wants to handle authentication.
Argh. That reminds me that I'm having trouble getting Win98 to talk to my Samba server (which is also serving Appleshare and NFS, of course, because I never got around to installing and configuring the Andrew File System). The WinNT machine can connect. The Win95 machine could connect until it ate itself and got moved to the repair pile. The Win2K machine can connect. It's just Win98 that doesn't want to. And I could swear I've solved this problem before and should have notes about it somewhere, but damned if I can figure out where said notes would be.
(no subject)
Basic operation for the server would be, listen on some obscure port, lines read from the socket would be URLs to display; display them by running
opera --whatevertheremotecontrolargumentis URLAnd then close the connection and go back to listening for connections. It'd probably be wise to add some sort of basic authentication though, like have the first line as a sanity check and the second line give a password or somesuch, and then only the *third* line be the URL for instance. And as some stupid sites insist on using whitespace in URLs (eg, Slashdot who should know better), you might want to escape the line you read before running the command. Perl can do that easily enough, but if using socket/netcat, you'd want to pass it through sed (yes that's IIRC available on Windows too) or something.
Hope this has given you some more ideas! Whether or not Opera is up to the task, Windows use shouldn't get in the way too much of getting such a thing done.