lacewing server login system

[dascribe]

Ok,

So I made a rough login system that works, but it got me to thinking…

The highscore extension does not have to create a separate file from the application to store the information.
It would be really cool to have something like that for lacewing as part of a simple login system.

Basically just make an extension like the highscore, that can hold 1 slot (or more).
That way the server could quickly verify a user login without having to go to a database or a text list.
The biggest advantages would include portability of the server and not having to worry about login security as much.
It could be it’s own extension, just like the highscore.
It would simply save the combination of the name, the delimiter, and the password was one string.

If you had 2 fields, one could include just the username to ensure no one is logged in 2 times.

Any thoughts?

[RickyRombo]

What?

I don't think I understand, but do you mean the Lacewing server verifies the user?

[dascribe]

A log in system
Where when you go to log on the server verifies that you are the right person.

[RickyRombo]

Why can't you just use a mySQL database? :confused:

What's wrong with the one you made at first, besides a file to store the information (which shouldn't ever happen anyway if you did it right -- read my tutorial)?

[Mathias]

With a chat we've been working on at AquadaSoft, we've written a pylacewing server where the client sets it's name to "name|passhash", and the accept name handler is delayed. Then, when the user has been looked up, a response is sent (NameAccepted or NameDenied), and the real name of the user is then set by the server. This works really well, and an example is even included with pylacewing (examples\mmf\account_server) that you can have a look at

[LB]

The highscore extension does not have to create a separate file from the application to store the information.

Actually, it does. It saves the file in your Application Data folder for your user profile. It's just an INI file.

[dascribe]

Twas just a thought

I never noticed the ini
I hadn't checked out the mysql thing recently. The last time I tried messing with it, I ended up yelling at the kids. :S

The whole idea though was to just have a quick reference sheet to log people in. I figured downloading the other data a player may have is less time sensitive.

The system I've set up does work, though it is not as flawless as I hope to make it.

I just dread the thought of trying to confirm the e-mail of a new registered user.

It may be my host that I use, but whenever I setup a forum, that thing drags like crazy and it uses the mysql.