From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: hearing the audio from a remote system
Date: Sun, 8 Oct 2000 19:13:51 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0010081908490.789-100000@localhost.localdomain> (raw)
In-Reply-To: <000801c031a4$8e410fc0$9c059ed8@wang>
I fail to understand how this scheme could possibly help real time. Unless
that is, you are stuck with an ISP with limited connectivity and happen to
have a fast connection to some server which has a better ISP.
The other posibility is if you could get permision to setup a damaen
capable of translating a stream into a lower bandwidth stream to which you
then connect via the new streams software.
But either of these are really a large task to be undertaken and not
likely to happen unless you happen to run your own co-located server, or
have a friend who runs one. I just can't imagine an administrator
leisurely handing out such permsions. And if you are at the point of
asking if this can be done via telnet, I doubt you are proficient enough
to be ready for the task.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
It's not reality that's important, but how you perceive things.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
Brent Harding
` Tommy Moore
` Brent Harding
` Kirk Wood
` Charles Hallenbeck
` Chris Nestrud
` Brent Harding
` Victor Tsaran
` Chris Nestrud
` Brent Harding
[not found] ` <Pine.LNX.4.21.0010080834250.789-100000@localhost.localdoma in>
` Brent Harding
` Kirk Wood
[not found] ` <Pine.LNX.4.21.0010081428270.789-100000@localhost.localdoma in>
` Brent Harding
` Kirk Wood
[not found] ` <Pine.LNX.4.21.0010081644540.789-100000@localhost.localdoma in>
` Brent Harding
` Victor Tsaran
` Brent Harding
` Victor Tsaran
` Kirk Wood [this message]
` Brent Harding
` Victor Tsaran
[not found] ` <Pine.LNX.4.21.0010081908490.789-100000@localhost.localdoma in>
` Brent Harding
` Geoff Shang
` Brent Harding
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=Pine.LNX.4.21.0010081908490.789-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).