From: KOVACS Krisztian <hidden@sch.bme.hu>
To: Harald Welte <laforge@netfilter.org>,
KOVACS Krisztian <hidden@balabit.hu>,
Netfilter-failover list <netfilter-failover@lists.netfilter.org>,
netfilter-devel <netfilter-devel@lists.netfilter.org>,
jamal <hadi@cyberus.ca>
Subject: Re: [RFC] ct_sync 0.15 (corrected)
Date: Sun, 22 Aug 2004 22:43:26 +0200 [thread overview]
Message-ID: <20040822204326.GA25567@sch.bme.hu> (raw)
In-Reply-To: <20040819110646.GJ3921@sunbeam.de.gnumonks.org>
Hi,
On Thu, Aug 19, 2004 at 01:06:46PM +0200, Harald Welte wrote:
> > So, do anyone know of anything which could be used by ct_sync?
> > (It has to be a semi-reliable, connectionless multicast protocol
> > with a _very_ low overhead.)
>
> everything I've seen so far about reliable multicast is inherently
> complex.
Oops, I've just found TIPC. Does anyone know enough details of TIPC to
judge if its reliable multicast service would be useful for us? I've just
downloaded the IETF draft, and it seems to me that the reliable multicast
service provided by TIPC may be useful (section 2.9 of the draft). Any
ideas?
The SourceForge URL:
http://sourceforge.net/projects/tipc/
--
KOVACS Krisztian
next prev parent reply other threads:[~2004-08-22 20:43 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 14:26 [RFC] ct_sync 0.15 (corrected) KOVACS Krisztian
2004-08-19 11:06 ` Harald Welte
2004-08-19 12:13 ` KOVACS Krisztian
2004-08-26 10:00 ` Jozsef Kadlecsik
2004-08-26 11:12 ` KOVACS Krisztian
2004-08-26 11:39 ` Jozsef Kadlecsik
2004-08-26 16:14 ` [nf-failover] " KOVACS Krisztian
2004-08-19 12:13 ` KOVACS Krisztian
2004-08-19 16:13 ` Henrik Nordstrom
2004-08-22 20:43 ` KOVACS Krisztian [this message]
2004-08-24 18:37 ` Harald Welte
2004-08-25 11:41 ` jamal
2004-08-22 0:40 ` Patrick McHardy
2004-08-22 7:49 ` [nf-failover] " KOVACS Krisztian
2004-08-22 20:42 ` Sven Schuster
2004-08-23 9:51 ` Patrick McHardy
2004-09-02 5:10 ` Willy Tarreau
2004-09-02 12:39 ` KOVACS Krisztian
2004-09-24 2:42 ` jamal
2004-09-25 7:52 ` [nf-failover] " Harald Welte
2004-09-27 13:07 ` jamal
2004-09-27 13:30 ` KOVACS Krisztian
2004-09-27 13:39 ` Harald Welte
2004-09-28 2:41 ` jamal
2004-09-28 6:46 ` Henrik Nordstrom
2004-09-28 10:56 ` jamal
2004-09-28 12:24 ` KOVACS Krisztian
2004-09-28 12:35 ` Henrik Nordstrom
2004-09-28 12:57 ` KOVACS Krisztian
2004-09-28 13:14 ` jamal
[not found] ` <1096379957.1026.5.camel@jzny.localdomain>
2004-09-28 14:46 ` Henrik Nordstrom
2004-09-28 14:56 ` KOVACS Krisztian
2004-09-28 15:07 ` Henrik Nordstrom
2004-09-28 18:04 ` Sven Schuster
2004-09-28 18:47 ` Henrik Nordstrom
2004-09-28 20:57 ` Sven Schuster
2004-09-28 22:30 ` Tobias DiPasquale
2004-09-28 23:36 ` Henrik Nordstrom
2004-09-29 3:00 ` Tobias DiPasquale
2004-09-29 8:34 ` Henrik Nordstrom
2004-09-29 2:14 ` Jamal Hadi Salim
2004-09-29 8:12 ` Henrik Nordstrom
2004-09-29 11:13 ` Jamal Hadi Salim
2004-09-29 11:29 ` KOVACS Krisztian
2004-09-29 11:44 ` Henrik Nordstrom
2004-09-29 13:03 ` Jamal Hadi Salim
2004-09-29 13:41 ` Henrik Nordstrom
2004-09-29 14:23 ` jamal
2004-09-29 15:02 ` Henrik Nordstrom
2004-09-30 12:24 ` jamal
2004-09-28 13:58 ` Henrik Nordstrom
2004-09-28 14:24 ` Tobias DiPasquale
2004-09-28 11:58 ` Tobias DiPasquale
2004-09-28 12:11 ` KOVACS Krisztian
2004-09-28 12:31 ` Henrik Nordstrom
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=20040822204326.GA25567@sch.bme.hu \
--to=hidden@sch.bme.hu \
--cc=hadi@cyberus.ca \
--cc=hidden@balabit.hu \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter-failover@lists.netfilter.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.