On Fri, Oct 18, 2002 at 11:05:15PM +0000, r2q2 wrote: > I have an idea similar where also an SSK is used > but DCHKs (dated content hash keys) are inserted by the streamer > and the nodes retrieve each CHK in a series. Eventually the CHK's would > expire on > their own. Each CHK would be the size of an given timeslice > ( 16 kbps 256 kbps) which would be the bit rate of the > encoded media. Each CHK has the time of insertion in hex. So > the streaming program would request S3K( streaming subspace > key)@(insert public key)/stream//(insert current time in > hex) and then put the data using the RSTP accepting and > listening on port 9000. Then you would take for example your > mp3 program and connect it to port 9000. > I wonder if this idea is any good. Why bother? Just insert 1 hour chunks at 16kbps, and let them expire naturally - this way you get free archiving, and the data will expire when it is no longer needed. We're talking about ~ 7MB/hour, so each hour will fit into one 8MB chunk (freenet rounds to powers of two)... or one 256kB chunk for every two minutes. This can all be done client side, and the auto-expire functionality really doesn't buy you much. And it will be slow. Expect to have to buffer tens of minutes in advance. >
-- Matthew Toseland [EMAIL PROTECTED] [EMAIL PROTECTED] Freenet/Coldstore open source hacker. Employed full time by Freenet Project Inc. from 11/9/02 to 11/11/02. http://freenetproject.org/
msg04479/pgp00000.pgp
Description: PGP signature
