BTW if the problem is that Valve do not want to use servers to pass
along the information then why not then only use the Content Providers
who I think are well and truly vetted before they are allowed to be
STEAM Content Providers AND more or less rule 99.999999999% of
wannabe's out when the question is. "Do you have a 1Gb or greater
link? Do you have a problem serving 10GB of data per day?"

On Wed, 15 Dec 2004 16:09:39 +0000, Stephen Moretti (blueyonder)
<[EMAIL PROTECTED]> wrote:
> Whisper wrote:
>
> >Well the thing is, your STEAM_ID is connected to your Login.
> >
> >Suipposedly you cannot create (RDRR many lols) a STEAM Login without a valid 
> >CD Key
> >
> >Thats how integrity is supposed to be maintained to allow people to login on 
> >any computer.
> >
> >
> Indeed - hence the reason I suggest checking userid and steamid and cd
> key all together.  If they don't match ie. someone is most likely
> interfering in some way (not so much the CD Key for reason I've already
> stated) don't let them in. If you're checking all the account details
> from both the client and from server that a user is connecting to you've
> got a much small probability of a hacker/cracker getting a valid
> combination and being able to access a game server.
>
> >Actually Access 2003 is really limited to 2GB size not so much records or 
> >anything like that, if you know what I mean.
> >
> >
> Aye - still a canny few records though ;o)
>
> >I think the limits for mySQL and MS SQL are more hardware limitations than 
> >anything else or more importantly budgetary :D
> >
> >
> ~lol~ yep - hence the reason why most of the stuff I build is based on
> mySQL :D
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to