Date: 25 Jun 1999 18:26:28 +0200 From: Frode Vatvedt Fjeld <frodef@acm.org> To: freebsd-multimedia@freebsd.org Subject: Re: bt848 channel frequencies Message-ID: <2hemj0b617.fsf@dslab7.cs.uit.no> In-Reply-To: Chris Doherty's message of "Sat, 26 Jun 1999 09:08:20 -0700" References: <Frode Vatvedt Fjeld's message of "25 May 1999 20:45:09 %2B0200"> <2hzp2tfr3t.fsf@dslab7.cs.uit.no> <374AA5BB.7C87D8C2@cs.strath.ac.uk> <2hogj9f0p6.fsf@dslab7.cs.uit.no> <3.0.6.32.19990626090820.007ad510@alicia.nttmcl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Doherty <cdoherty@nttmcl.com> writes: > this in particular (at least in the US, especially as telecom > deregulation has ever-greater effect) is a difficult task at best, > with multiple cable companies in the same area (occasionally > overlapping) and coverage areas being not necessarily contiguous; > also the same company will have different channel lineups in > different geographical areas that are sometimes close together. I didn't mean that there will be a one-to-one mapping from geographical location to frequency-set, only that the frequency-sets should have names that suggest where in the world (and possibly cable provider etc.) they are likely to apply. The basic idea is that any one user is likely to use a small number (one or two) frequency-sets, and that many (thousands) other people likely will use the same sets. How about if every frequency-set is associated with (at minimum) tags that identify country, city, type (antenna/cable) and provider. This way a user/application can make simple queries in order to find his frequency-set quickly. -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2hemj0b617.fsf>