EntropiaTracker.com Official Thread

[Teranoz]

Tested for simple sql injections : safe...


Hmm should that mean a :-) or a :-(

[aridash]

Originally Posted by Starfinder

If anyone wanna help me run the program .. let me know, i think my laptop (which is running the program now, is starting to sweat - its somewhat warm after 3 days of nonstop PE.. lol -- also if it CTD's it dosent login again (the whole EULA thing))

If you wanna run the program please pm me, and I will send you the program as well as the source code (if you dont trust me you can read the source code your self, and compile it into an exe file)

Its a bit tricky tho - since I have but somewhat much efford into making the algorithms, and I dont want everyone to parse the data into their own databases based on my code -- prehaps we can get 3-4 independant ppl to read the code and approve it?

it occurs to me that distributing the program may circumvent both the EULA and single machine problems. If many people run the app and upload to a central DB server, which can sort the duplicates before populating the DB (maybe two, one logging all entries so you can correct any errors), which in turn can be read by a client.

[Droops]

Nice Thanks

[Witte]

Originally Posted by aridash

it occurs to me that distributing the program may circumvent both the EULA and single machine problems. If many people run the app and upload to a central DB server, which can sort the duplicates before populating the DB (maybe two, one logging all entries so you can correct any errors), which in turn can be read by a client.

Seems to me you will indeed need at least around 5-10 logged in clients to make this relyable. The system can be made so that at most 10 people connect to the server at the same time, while all other clients just idle untill one of the 10 disconnects.

[Starfinder]

the "client" ive made IS made to be part of a larger network.
It checks everything with the database before sumbitting anything.

There however is a small "mem leak" in the application (nothing your computer cant handle - im more worried about my server) The client wont close the connection to the database until the garbage collector does it.. and it keeps the connections open for 30 seconds, but it creates a new connection every 3 second.... So imagine 50 clients...

thats 30/3 * 50 = 500 connections to my server, even tho only 10 of them might be used... = my server will hate me forever.

Via the MS SQL manager the server laggs with just 2 clients connected... lol..

Anyways.. tweaking the program tonight... anyone wanna run it.. let me know and ill send you a manual on how to get it workin / best OCR results.

[Witte]

Originally Posted by Starfinder

the "client" ive made IS made to be part of a larger network.
It checks everything with the database before sumbitting anything.

There however is a small "mem leak" in the application (nothing your computer cant handle - im more worried about my server) The client wont close the connection to the database until the garbage collector does it.. and it keeps the connections open for 30 seconds, but it creates a new connection every 3 second.... So imagine 50 clients...

thats 30/3 * 50 = 500 connections to my server, even tho only 10 of them might be used... = my server will hate me forever.

Via the MS SQL manager the server laggs with just 2 clients connected... lol..

Anyways.. tweaking the program tonight... anyone wanna run it.. let me know and ill send you a manual on how to get it workin / best OCR results.

It seems a bit unefficient to make the client check with the server before submitting. Isnt just sending the data, and let the server process it a lot more efficient? Or is it a direct connection to the SQL server? In that case I think you can better make a webservice that handels the clients.

ps, I turned off globals in chat and I like it. So I cant help you out in this. I am interested though in your sourcecode . I made a realtime OCR myself that parses the damage you do and logs it. Although it uses very simply algorithms. So I am kinda curious how you approached it.

[Starfinder]

its directly connected to the SQL server.
Due to the nature of the data structure it only have to make 1 SQL command to know if it should insert data or not. the SQL will either return 0 or 1, dont think a webservice can do that much more efficient.

[Witte]

Originally Posted by Starfinder

its directly connected to the SQL server.
Due to the nature of the data structure it only have to make 1 SQL command to know if it should insert data or not. the SQL will either return 0 or 1, dont think a webservice can do that much more efficient.

I dont know what your plans are, but I was thinking there might be more people interested in the chatlog function, which opens the door to maybe 100-1000 clients at the same time. In that case some sort of connection controll would be nice

ps. when you set the relevant columns to key value you should not even need to check, it will simply not insert in case of duplicates.

[Starfinder]

well.. its kinda hard to have duplicates when you include time as well

3 seconds isent much time span... so the same global will be OCR'ed at time X.. and at time X + 3 seconds... so it wont be the same entry hence i need to check that the same global hasent been inserted into the database in the past 10 min or so (which means that the same person cant global on the same mob with the same value twice or more in 10 min...)

[sitram]

Perhaps you can make a small client application that ppl can use to send information about globals to your server.

The server doesn't have to parss all the information it recieves from the clients, but to return a stand by message if it has already 1-2 clients connected(or as much as it can handle). The client then will check back with the server ever few seconds, this way it doesn't create a huge traffic with the server.

I don't see any problem with breaking EULA with this, because the information will be gathered from all the players in EU and the client doesn't interfere with Entropia Universe.

It might raise a problem of privacy, but if the person that installs the client will check a button to give his accept that he wants to send the images to the server, I think this will be solved too.

Perhaps in time there will be a dedicated server that handles all the clients and further development can be made to improve the usage of all the gathered data.

Just a few quick ideas from,
Sitram