From: Nick <nick@fluffyspider.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [Fwd: streaming problem]
Date: Thu, 12 Sep 2002 01:18:22 +0000 [thread overview]
Message-ID: <marc-lartc-103179357930392@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103173197330780@msgid-missing>
Hi,
This may or may not be what your looking for.
Rather than finding some complex routing solution, you just need a proxy
sitting on the machine what sits between the fast and slow connection. It
makes a single connection to the camera and serves multiple connection to
anyone else on the 100mb connection.
I've used a camera server called 'camserv' and it comes with a utility
proxy for just this type of thing. Give it a go. The only other thing I
can think you might want to do is route connections going the cameras
source to the proxy so users don't need to know its not a dedicated
connection.
Nick
On 11 Sep 2002, skuda wrote:
hi all :), i have a problem, i have 2 servers, with linux and apache
1.3.26 in it, one (A) have a slow connection 64kbit isdn, and the other
(B) have a fast connection 100mbit, in A i have motion
(http://motion.technolust.cx/) sharing a webcam in port 8001 and a java
applet (cambozola) to show in the index of the webserver the camera in
real time, i would like connect the fast (B) to the slow connection (A)
and share with many people this camera without open more than one
connection from (B) to (A), because bandwith is too little to open many
connections with B. Do you know any solution to this problem? thanks in
advance
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-09-12 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 8:12 [LARTC] [Fwd: streaming problem] skuda
2002-09-12 1:18 ` Nick [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=marc-lartc-103179357930392@msgid-missing \
--to=nick@fluffyspider.com.au \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.