Reply to thread

Message

<blockquote data-quote="zeflash" data-source="post: 80426" data-attributes="member: 13641">Well, I talked a bit a while ago with the meetvshow guy about how things were working, and his approach of how the exchange works between the server data &amp; the client is not efficient. Here is the problem: the server parses the tvshow websites to keep the info up to date.The client connects to this server to get up to date info.How does the client/server know what to retrieve/send if something was changed&nbsp; on the website? His approach is that the client plugin should retrieve back all shows, on every check, if the info is less than 3 weeks old.Wrong design! That just kills the bandwidth on the server side and it doesn't ensure that 100% of the client data is up to date.So in the end everyone is killing all the local db once in a while &amp; retrieve everything back.Of course, having a central server that would concentrate all the necessary information from the shows would be more efficient than having every client parse the data itself.Trouble is, someone has to host this server, keep the data up to date, and pay for the bandwidth. If for any reason the server dies, everyone is hurt, too.So it's a much more complicated project. Interesting one though.I'd say, let's make it work fairly well locally first, and thing of enhancements afterwards.</blockquote>

[QUOTE="zeflash, post: 80426, member: 13641"] Well, I talked a bit a while ago with the meetvshow guy about how things were working, and his approach of how the exchange works between the server data & the client is not efficient. Here is the problem: the server parses the tvshow websites to keep the info up to date. The client connects to this server to get up to date info. How does the client/server know what to retrieve/send if something was changed on the website? His approach is that the client plugin should retrieve back all shows, on every check, if the info is less than 3 weeks old. Wrong design! That just kills the bandwidth on the server side and it doesn't ensure that 100% of the client data is up to date. So in the end everyone is killing all the local db once in a while & retrieve everything back. Of course, having a central server that would concentrate all the necessary information from the shows would be more efficient than having every client parse the data itself. Trouble is, someone has to host this server, keep the data up to date, and pay for the bandwidth. If for any reason the server dies, everyone is hurt, too. So it's a much more complicated project. Interesting one though. I'd say, let's make it work fairly well locally first, and thing of enhancements afterwards. [/QUOTE]

Verification