Hashing

[Meh]

I didnt write this but found it on my travels.

http://www.rival.bnetweb.com/rival/content.php?article.24

That link is an article on how to hash a connection to battle.net.

[Zakath]

It's not really much of an article. More a long example of not-incredibly-well-written code.

[MyndFyre]

This might be pertinent in BNBDR, but I noticed that while it says "tutorial" it screams "be a cookie cutter code copycat."

There is nothing there that actually *teaches* what is involved in hashing Battle.net.  It is also not language-agnostic.  Language agnosticism in a tutorial is not a requirement, but it is when all you do is give code.

[edit]You just beat me Zak.

[Zakath]

[edit]You just beat me Zak.

Arrrr, that I did!

Oh man..."you must have setup.ini"

Oh no! My method for storing configuration information (using the windows registry) won't work if I want to create a hashed client?!

Shit, I don't remember importing either of those DLLs, either!

[Meh]

I only found it, as i said i didnt write. I thought it may be useful for others to look and see how its done.

[iago]

I don't like using the registry to store information, personally.  But that's personal preference, and an argument for another time/place

[MyndFyre]

I only found it, as i said i didnt write. I thought it may be useful for others to look and see how its done.

I know that.  I'm saying that it's not useful as a tutorial.  It's copycat code.

I don't like using the registry to store information, personally.  But that's personal preference, and an argument for another time/place

Did we ask for your opinion on using the registry?    Out of curiousity, why not?

[Meh]

I only found it, as i said i didnt write. I thought it may be useful for others to look and see how its done.

I know that.  I'm saying that it's not useful as a tutorial.  It's copycat code.

I don't like using the registry to store information, personally.  But that's personal preference, and an argument for another time/place

Did we ask for your opinion on using the registry?    Out of curiousity, why not?

My comment was aimed mainley at Zakath. I felt I was beeing flamed for something I did not desrve.

[Zakath]

My comments were aimed more at that "tutorial," not at you Meh.

[iago]

I don't like using the registry to store information, personally.  But that's personal preference, and an argument for another time/place

Did we ask for your opinion on using the registry? Out of curiousity, why not?

1. I format frequently, and it's much easier to back up programs that don't have a presence in the registry.
2. Programs are more easily ported to/used in Linux if they don't use the registry.
3. It's much easier to find/edit configurations by hand if they are files.  Unless they put the files somewhere stupid. but eh.

<edit> If you want to persue this, let's start a new thread somewhere.

[Zakath]

1. I format frequently, and it's much easier to back up programs that don't have a presence in the registry.

See, I consider formatting a time consuming nuisance. I do it as infrequently as I can practically manage.

2. Programs are more easily ported to/used in Linux if they don't use the registry.

This is a chat client that is completely based on the Windows API we're talking about here. There'd be no point in porting it to linux; it'd make far more sense to just write a new one from scratch.

3. It's much easier to find/edit configurations by hand if they are files.  Unless they put the files somewhere stupid. but eh.

Pfft...what are you doing editing these things by hand, anyway? That's what the config dialog is for.

[MyndFyre]

3. It's much easier to find/edit configurations by hand if they are files.  Unless they put the files somewhere stupid. but eh.

Pfft...what are you doing editing these things by hand, anyway? That's what the config dialog is for.

<hypocritical-statement reference="signature">Pfft, Windows newbie.</hypocritical-statement>