bitbanger
04-10-2009, 04:14 AM
I have been reading everything I can find about the Slinger IKS but I haven’t found any detailed theory of operation. I have read a lot about the overview operation of which basically the receiver requests authentication from the card which is extracted from the ROM image and whatever the ROM image cannot provide is requested from the sub’d client Slinger. Note: when I use the terms server and client in the following I am referring to the Slinger units not the ISP internet system.
I have a Slinger on order awaiting the next build release from the mfgr which will be shipped next week. I have read there is a lot of freezing occurring; some of which has been attributed to the user ISP while the rest being attributed to new product debug.
That being said, I have a performance concern and theory of operation questions relating to the concern.
With the release of the next build, not knowing if the build is for a few hundred or thousands of units, how will the increase of new products accessing the Slinger server unit(s) affect the freezing situation. Is the freezing attributed to Slinger server unit overload or internet delays or just new product development or what??
Another question would be is how often is the receiver requesting authorization from the card –miliseconds, seconds, minutes,………….
Not knowing the detailed theory of operation, I can picture two scenarios:
When required, the client requests specific authorization data based on the channel selected and only receives the data required for that channel all of which is dependent on the receiver numbers. The bandwidth being eaten up by all the client specific data sent, the server having to crunch that data and then transmit it back to the client.
Or
When required, the client requests authorization data from the server and the server dumps all the data it has and the client sorts out what is applicable to its needs.
Where I am going with this is the bandwidth required to access the server from thousands of clients(if indeed that is the freezing issue cause). Would the system be more efficient if everyone used the same receiver numbers and instead of the thousands of clients having to request data, the server could just continually broadcast the data and let the client sort out what it needs. Could we have a fast server channel for public numbers and another channel for more specific private numbers that require more bandwidth?
Am I a clueless newbie or am I thinking on the right track for a serious tester????
Thank You Very Much for your time and responses
I have a Slinger on order awaiting the next build release from the mfgr which will be shipped next week. I have read there is a lot of freezing occurring; some of which has been attributed to the user ISP while the rest being attributed to new product debug.
That being said, I have a performance concern and theory of operation questions relating to the concern.
With the release of the next build, not knowing if the build is for a few hundred or thousands of units, how will the increase of new products accessing the Slinger server unit(s) affect the freezing situation. Is the freezing attributed to Slinger server unit overload or internet delays or just new product development or what??
Another question would be is how often is the receiver requesting authorization from the card –miliseconds, seconds, minutes,………….
Not knowing the detailed theory of operation, I can picture two scenarios:
When required, the client requests specific authorization data based on the channel selected and only receives the data required for that channel all of which is dependent on the receiver numbers. The bandwidth being eaten up by all the client specific data sent, the server having to crunch that data and then transmit it back to the client.
Or
When required, the client requests authorization data from the server and the server dumps all the data it has and the client sorts out what is applicable to its needs.
Where I am going with this is the bandwidth required to access the server from thousands of clients(if indeed that is the freezing issue cause). Would the system be more efficient if everyone used the same receiver numbers and instead of the thousands of clients having to request data, the server could just continually broadcast the data and let the client sort out what it needs. Could we have a fast server channel for public numbers and another channel for more specific private numbers that require more bandwidth?
Am I a clueless newbie or am I thinking on the right track for a serious tester????
Thank You Very Much for your time and responses