Was talknig to a friend today, about the virtues of the dreambox, i asked a question about resharing, as i found it quite interesting reading the tutorial on CS.
i said so 1 server and 15 clients, you have to make sure the server stays on to share the original share card, but when you get a good few of them all watching at the same time you can get breakup, especially if theres a good few more clients than 15, say 50.
So i assumed that the limit on clients is based on the limit of your upstream from your original card server, as the upstream on the majority of home based broadband internet connections is 2 meg, not a lot really when you have 50 clients accessing it, (although i dont know the individual bandwidth of the data use per client but i'll find out no doubt after this post) so i said how about daisy chaining your units instead of 1 fline, thats fine if the box thats giving the reshare but if 1 of the daisylinked boxes was turned off then all the boxes after that box would go off also.
ok then
so why cant a subroutine be writtten in so that if the predecessor box went down it looked somewhere else for another fline? can you write multiple fline into the boxes, i dont know, i am new to this my expertise is in webdesign, i thought that this just might work to solve the bandwidth problem as each client would have a 2 meg upload to its next client in line, a bit like cloud computing, but you would need the redundancy if a client went down
SB
i said so 1 server and 15 clients, you have to make sure the server stays on to share the original share card, but when you get a good few of them all watching at the same time you can get breakup, especially if theres a good few more clients than 15, say 50.
So i assumed that the limit on clients is based on the limit of your upstream from your original card server, as the upstream on the majority of home based broadband internet connections is 2 meg, not a lot really when you have 50 clients accessing it, (although i dont know the individual bandwidth of the data use per client but i'll find out no doubt after this post) so i said how about daisy chaining your units instead of 1 fline, thats fine if the box thats giving the reshare but if 1 of the daisylinked boxes was turned off then all the boxes after that box would go off also.
ok then
so why cant a subroutine be writtten in so that if the predecessor box went down it looked somewhere else for another fline? can you write multiple fline into the boxes, i dont know, i am new to this my expertise is in webdesign, i thought that this just might work to solve the bandwidth problem as each client would have a 2 meg upload to its next client in line, a bit like cloud computing, but you would need the redundancy if a client went down
SB
Last edited: