From: andrzej zaborowski <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu - where will it go?
Date: Sat, 14 Jan 2006 20:32:54 +0100 [thread overview]
Message-ID: <fb249edb0601141132j4fe9fc2bn@mail.gmail.com> (raw)
In-Reply-To: <200601141132.03700.info@j-pfennig.de>
Hi,
> - define a protocol to use qemu over a network (should multiplex
> video, sound, usb, serial and so on).
>
> So you see: in a commercial and or industrial application one would like to run
> the qemus on a server. At least the MS remote desktop protocol should work
> well. A qemu specific client would be nicer.
>
> Please do not try to make the current qemu program a better GUI application -
> do it the other way: move SDL out of qemu and write an extra client app!
>
I'm not a QEMU developer but I don't think QEMU is seeking commercial
and or industrial popularity (I might be wrong though). Personally I'd
rather be trying to keep it small and do its own task well rather than
reimplement in QEMU parts of other programs' tasks. The universal
rules of writing cross-platform software clearly show that
dependencies on other packages (libraries, utilities) are a good
thing. It's also one of the UNIX traditions to have big tasks divided
into small parts and each of them be carried out by a different tool.
So I think the existing protocols should be used for remote control,
SDL supports several different frontends for audio and video and many
of them already offer full network transparency (X, esound), and for
USB, other, platform-specific mechanisms can be used for remote
devices (like the Linux network block/character devices support).
I agree with your other points.
Regards,
Andrew
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
next prev parent reply other threads:[~2006-01-14 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 10:32 [Qemu-devel] Qemu - where will it go? Juergen Pfennig
2006-01-14 17:35 ` Thomas Steffen
2006-01-14 19:20 ` Oliver Gerlich
2006-01-15 7:37 ` Wesley Parish
2006-01-16 15:48 ` Paul Brook
2006-01-14 19:32 ` andrzej zaborowski [this message]
2006-01-15 17:55 ` Fabrice Bellard
2006-01-16 13:52 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb249edb0601141132j4fe9fc2bn@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).