Originally by: James Duar
What's needed is a "Signature Hash" field.
Basically, give each sig a unique ID so you can follow what you're doing more easily. Then have the client remember what a sig is once the details start filling out (i.e. the description and the type).
This shouldn't(tm) bee to diffcult to implement because I would venture to be that easch sig, at least per system, is identified by a unique id of some sort. It just wouls be a matter for the client to rember the id, loc, and type. Then that data would be stored in a hash on the client side untill the client logs off(or even a temp file). There would be no need for the server to be involed with this no extra db stuff, because it is all stored client side.
This would give the log with out extra load on the server because the client already has that info. And the client should not be able to requery for that sig unless they happed to scan it out again. Therfor the user won't know if the sig is really still there untill they warp to it.
A time stamp when the sig was last found, its type, and the ability to click on it and display it in the solarsystem map would rock.