From: Marc Manthey <marc@let.de>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Its the bufferbloat stupid
Date: Thu, 25 Aug 2011 22:01:13 +0200 [thread overview]
Message-ID: <784A08F2-BF2D-4672-937A-250934BA51D5@let.de> (raw)
In-Reply-To: <CAA93jw7D2+gKp4paAjFMR2zyjnubN=OiLgEhvVNC+bEmSm2U3Q@mail.gmail.com>
Hey dave, all
today i had the time to listen to this google tech talk again
http://www.youtube.com/watch?v=qbIozKVz73g (Bufferbloat: Dark Buffers
in the Internet )
and i metioned the sentence from vinf cerf in the introduction to Jim
Gettys
"....he is working on emerging teleconferencing " whitch came to my
interest.
I am doing videoconferencing since the early 90s and i am researching
in the past years about large scalable secure
video conferencing a lot.
After i meet my main developer in 2008 we started to implement
"opencu" based on the old protocol papers i´ve found.
At that time there was no efficent opensource codec and Qt wasnt
opensourced too, so we decided to use wxwidgets and xvid / portaudio
to implemented the basic features and made an proof of concept client.
(The server/refector isnt re_enineered yet, only java hack available )
He got a job offer to implement such a commercial system but he failed
after some attemts on latency and serverload.
So after i' ve tested most of all available systems like paltalk,
ivisit, camfrog and jmeeting, webmeeting and so on , i figured all
solutions
whitch were mostly implemented in the 90s worked more or less worse
and had latency about 4 seconds and were not opensource at all.
So I decided to re_implement our social -zero-conferencing idea with
VP8 whitch was aquired from google in 2010 and got "opensourced"
and seems highly efficent for the video part and WAB bonjour a
zeroconfiguration service discovery framework developed
by dr.steward chesire from apple.
After i see the issues my developer had, this "unbufferbloat project"
came to my attention because latency and buffering seems to be the
main issue in realtime communication plattforms.
I am looking forward to see how this problems would be solved.
regards
Marc
On Aug 25, 2011, at 4:18 AM, Dave Taht wrote:
> oops, the thing I was hoping for more eyeballs on was:
>
> http://www.bufferbloat.net/issues/249
>
> in addition to 243.
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://the-edge.blogspot.com
>
-- Les enfants teribbles - research / deployment
Marc Manthey- Vogelsangerstrasse 97
50823 Köln - Germany
skype: MarcManthey
Tel.:0049-221-29891489
Mobil:0049-1577-3329231
site: http://let.de
project : http://opencu.org
twitter: http://twitter.com/macbroadcast/
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).
prev parent reply other threads:[~2011-08-25 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 2:04 Cerowrt RC6 plan Dave Taht
2011-08-25 2:18 ` Dave Taht
2011-08-25 20:01 ` Marc Manthey [this message]
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=784A08F2-BF2D-4672-937A-250934BA51D5@let.de \
--to=marc@let.de \
--cc=bloat-devel@lists.bufferbloat.net \
/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