[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-multimedia
Subject:    Re: aRts needs to be replaced (was Re: Disabling aRts in knotify)
From:       Scott Wheeler <wheeler () kde ! org>
Date:       2004-02-19 18:16:25
Message-ID: 200402191916.32819.wheeler () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(Moving this to kde-multimedia too -- please respond there.)

On Thursday 19 February 2004 19:03, Alexander Neundorf wrote:

> I really don't think so. It's a design fault. We could also write a 
> webbrowser which implements html, http, tcp, ip all itself (ok, slightly 
> exaggerated ;-) 

Right, but you're the one suggesting to write such a web browser.  ;-)

That's my point.  I'm not arguing that this stuff should be in the server, I'm 
just saying that it shouldn't be in the apps.

> e.g. for network transparency.

Actually here's one advantage of decoding on the server in theory -- you can 
send the encoded (much smaller) data over the network rather than the raw 
audio.

> > I don't care whether you chose to use a soundserver or not, and I'm not
> > sure if that's what you're getting at, but there needs to be something
> > available to multimedia programmers in KDE that handles these common media
> > tasks (decoding, playing, buffering, etc.).
> 
> Yes.

Ok, we seem to be converging here...

- -Scott

- -- 
The three chief virtues of a programmer are: laziness, impatience and hubris.
- --Larry Wall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFANP15Qu0ByfY5QTkRAt36AJ9psUdZHyI5otL5UWGG0IK47m4QmACeMqDB
1EcKrJcjtz0VGzhmpxKBycc=
=yKLz
-----END PGP SIGNATURE-----
_______________________________________________
kde-multimedia mailing list
kde-multimedia@kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia

[prev in list] [next in list] [prev in thread] [next in thread]