Date: Thu, 03 Jun 2004 02:31:59 +0900 From: Saber ZRELLI <zrelli@jaist.ac.jp> Cc: freebsd-hackers@freebsd.org Subject: Re: suggestions ? Message-ID: <40BE0F0F.6030805@jaist.ac.jp> In-Reply-To: <40BE0C13.309@pacific.net.sg> References: <40BDF377.4000900@jaist.ac.jp> <40BE05C0.1090807@pacific.net.sg> <40BE092F.9090402@jaist.ac.jp> <40BE0C13.309@pacific.net.sg>
next in thread | previous in thread | raw e-mail | index | archive | help
Erich Dollansky wrote: > Hi, > > Saber ZRELLI wrote: > >> >> Erich Dollansky wrote: >> >> >>> Hi, >>> >>> Saber ZRELLI wrote: >>> >>> >>>> Hello Dear Seniors , >>>> i was looking for some interesting issue related to FreeBSD >>>> networking , >>>> to make it my master thesis , but i couldn't find such a topic , >>>> certainly because i'm not a FreeBSD expert ( but i will be =) ) , >>>> so could any member here , especially contributors , i'm sure you have >>>> very rich ideas and cool stuff to offer ... >>>> >>>> i was thinking about implementing Robust TCP/IP connections .. but >>>> somebody told me that is not very consistent , and i think so also , >>>> >>> >>> Did you consider fault-tolerant TCP/IP connections to multiple servers? >> >> >> >> i don't see the difference between connections to one or to multiple >> servers , it's still TCP/IP connections between two nodes. >> I'm i wrong ? >> > If multiple servers provide the data, it should not matter which server > provides it. I see what you mean , you are talking at higher level , when i mentioned Robust TCP/IP i meant TCP connections in the kernel network stack level , the architecture you are talking about is like a middle ware handeling all TCP/IP connections for a client to multiple servers. the mechanism is something like buffereing data in the network stack as prevention for eventual connection problem , when that problem happens and is detected , the Net. stack will try to reconnect ( while buffering the user data ) , once the connection is reistablished the buffered data will be sent and the user wont notice nothing ( if the outage time is not huge of course ). that may sounds stupid , but that's what i'm thinking about. But it must made sure that only servers are taken to > deliver the data which have their data updated. It is a pretty complex > process to keep the data consistent on all servers. > > If the connection is only to a single server and this single server > fails, the client does not get any data any more. If the connection is > to multiple servers and at least one of the servers is still up and > running, the client still has a chance to get its data. > > Erich > > -- Saber ZRELLI. Japana Advanced Institute of Science and Technology School of Information Sience. Katayama Lab mail : zrelli@jaist.ac.jp, saber_z@fastmail.fm url : www.jaist.ac.jp/~zrelli gpg-id : 0x7119EA78
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40BE0F0F.6030805>