Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Khadhir Hashul
Paladins of the Final Frontier
3
|
Posted - 2014.04.29 07:07:00 -
[1] - Quote
They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible? |
Kaarous Aldurald
ROC Deep Space The ROC
5509
|
Posted - 2014.04.29 09:52:00 -
[2] - Quote
It actually does give some information, actually. So it's not "unnecessary".
For instance, it can tell you if someone swapped corp between two player corps, or may have been kicked out of their last one into an NPC corp.
Then you get to ask why.
As for being lag inducing, I will agree there. Try opening Psychotic Monk's corp history. The last time I did that it actually crashed my client. "Verily, I have often laughed at the weaklings who thought themselves good because they had no claws."
-áPsychotic Monk for CSM9.
|
Revolution Rising
Native Freshfood Minmatar Republic
390
|
Posted - 2014.05.12 05:04:00 -
[3] - Quote
I rarely leave corp and don't go into an NPC corp. Most of the time I am leaving a corp because of burnout and just want a rest from ... all the people ;)
I don't think you'd find too much "valuable information" in the NPC corps in my corp history. (I don't think I've EVER been kicked from a corp - altho it's been many years perhaps..)
CSM7 Skype Leak
|
Benny Ohu
Chaotic Tranquility
3205
|
Posted - 2014.05.12 05:19:00 -
[4] - Quote
Kaarous Aldurald wrote:For instance, it can tell you if someone swapped corp between two player corps, or may have been kicked out of their last one into an NPC corp. that info can also be gained from player corp join/leave dates, so nothing's lost by dropping npc corps from corp history
it might also be useful to allow players to set a default timeframe for the corp history display. for example, the default would be three months with a dropdown menu to increase that to six months, a year or all-time. the same way the market history works.
e: not knowing how computers or the client actually work, i imagine the client'd say to the server 'send me three months of player x's corp history' instead of asking for the lot |
Draconian Maass
Panhandle Industries Order of the Exalted
0
|
Posted - 2014.05.30 05:21:00 -
[5] - Quote
I think it wouldn't me much of a problem to see this info go away. But since we are on the subject. I think there can be more info on the corp log like whether or not someone was kicked or left mabe even some notes from the last employer like a resume. |
Malcanis
Vanishing Point. The Initiative.
15692
|
Posted - 2014.05.30 07:21:00 -
[6] - Quote
Khadhir Hashul wrote:They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible?
How do they cause lag?
"It is difficult to get a man to understand something, when his ISK/hr depends upon his not understanding it!" |
Benny Ohu
Chaotic Tranquility
3304
|
Posted - 2014.05.30 08:13:00 -
[7] - Quote
Malcanis wrote:Khadhir Hashul wrote:They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible? How do they cause lag? A long employment history can take an annoyingly lengthly time to load, and can disable your client in space. NPC corps add to the list, it's possible their inclusion increases the time the history takes to load. |
Khadhir Hashul
Dark Angel Empire
13
|
Posted - 2014.05.31 05:15:00 -
[8] - Quote
Malcanis wrote:Khadhir Hashul wrote:They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible? How do they cause lag?
Allow me to illustrate: http://www.youtube.com/watch?v=H5W0Dm0K95Q&feature=youtu.be |
Malcanis
Vanishing Point. The Initiative.
15713
|
Posted - 2014.06.01 12:32:00 -
[9] - Quote
Benny Ohu wrote:Malcanis wrote:Khadhir Hashul wrote:They're unnecessary lag-inducing clutter, especially if one changes corps more than once throughout their EVE career. They should be invisible in the employment history. Is there really any reason that they should continue to be visible? How do they cause lag? A long employment history can take an annoyingly lengthly time to load, and can disable your client in space. NPC corps add to the list, it's possible their inclusion increases the time the history takes to load.
Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order. "It is difficult to get a man to understand something, when his ISK/hr depends upon his not understanding it!" |
Meytal
School of Applied Knowledge Caldari State
424
|
Posted - 2014.06.02 16:26:00 -
[10] - Quote
Malcanis wrote:Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order. It's actually not just reading a few lines of text from the database.
At a minimum, it checks each corp in the list to determine whether that corp still exists or has since closed, resulting in multiple database calls between client and server. It may even do more than this behind the scenes that players aren't aware of.
|
|
Malcanis
Vanishing Point. The Initiative.
15760
|
Posted - 2014.06.02 17:11:00 -
[11] - Quote
Meytal wrote:Malcanis wrote:Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order. It's actually not just reading a few lines of text from the database. At a minimum, it checks each corp in the list to determine whether that corp still exists or has since closed, resulting in multiple database calls between client and server. It may even do more than this behind the scenes that players aren't aware of.
Those the kind of slow changing data that can be updated on a batch run eg: DT "It is difficult to get a man to understand something, when his ISK/hr depends upon his not understanding it!" |
Meytal
School of Applied Knowledge Caldari State
425
|
Posted - 2014.06.03 12:00:00 -
[12] - Quote
Malcanis wrote:Meytal wrote:Malcanis wrote:Huh I didn't know that. Sounds like some optimisation of what should be a pretty tiny text file reference is in order. It's actually not just reading a few lines of text from the database. At a minimum, it checks each corp in the list to determine whether that corp still exists or has since closed, resulting in multiple database calls between client and server. It may even do more than this behind the scenes that players aren't aware of. Those the kind of slow changing data that can be updated on a batch run eg: DT True, though you lose some accuracy. Only the closed corps can really be cached long-term if you want to be accurate.
And if we don't care about accuracy in this information anymore, there's no need to report it, really :) Which is actually an option: no longer report the "(closed)" status of corps in Employment History? Interested parties can always look up the corps themselves anyway. |
Tipa Riot
Federal Navy Academy Gallente Federation
6
|
Posted - 2014.06.07 18:05:00 -
[13] - Quote
IMO there are two major use cases for reading the corp history: 1) quick check about age and recent affiliations during fights or short encounters, and 2) careful evaluation in case of long term engagement or if high values are involved. The first has to be executed without lag, but you only need the birthdate and the last let's say 5 corps. For the second reason you can just offer a 'detailed' button which expands to the full info and may take some seconds. |
Iain Cariaba
In Over Our Heads
35
|
Posted - 2014.06.12 15:52:00 -
[14] - Quote
So cyno and cloaky camper alts get no employment history at all? If I agreed with you, we'd both be wrong. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |