TC:Nova Wipe 10/14/2010

[Lobreeze]

So, if deadlocks can't happen with the OR code, why on earth would you equate server status not updating to a deadlock?

And since when did examples stop having to makes sense? Isn't that the whole point? To make sense?

That will only going to cause confusion especially coming from someone with the title "SWGemu support helper"

[Vlada]

Originally Posted by Lobreeze

So, if deadlocks can't happen with the OR code, why on earth would you equate server status not updating to a deadlock

Not server status, that "thing"



that shows server status. And deadlock is one of the things that causes it to show incorrect server status. Server status and what causes server status changes is one thing, thing that shows server status is a completely different thing.

Originally Posted by Lobreeze

And since when did examples stop having to makes sense? Isn't that the whole point? To make sense?

Because it was not directly related to the OR code or server status but to the "thing" that shows server status. For one it doesn't make sense and doesn't need to make sense because i wasn't talking about them, for other it makes perfect sense because it explains that the "thing" showing the server status can in some cases show incorrect server status, one of them being a deadlock.

Originally Posted by Lobreeze

That will only going to cause confusion especially coming from someone with the title "SWGemu support helper"

No, not really. It simple shows that if you want correct server status you need to go to IRC #status channel and that LPE, those "things" even www. swgemu.org can sometimes be wrong.

Simple enough for you? I can dumb it down more if necessary.

[Lobreeze]

Originally Posted by Vlada

Not server status, that "thing"



that shows server status. And deadlock is one of the things that causes it to show incorrect server status. Server status and what causes server status changes is one thing, thing that shows server status is a completely different thing.



Because it was not directly related to the OR code or server status but to the "thing" that shows server status. For one it doesn't make sense and doesn't need to make sense because i wasn't talking about them, for other it makes perfect sense because it explains that the "thing" showing the server status can in some cases show incorrect server status, one of them being a deadlock.



No, not really. It simple shows that if you want correct server status you need to go to IRC #status channel and that LPE, those "things" even www. swgemu.org can sometimes be wrong.

Simple enough for you? I can dumb it down more if necessary.

Do you even know what you are saying?

How can that "thing" not update because of a deadlock if deadlocks no longer exist.

Why don't you just say "Server status thing isn't always accurate, use #status in IRC"

By saying that "thing" and swgemu.org

Originally Posted by Vlada

Those cant detect deadlocks.

is just stupid. Now anytime those don't update you're going to get people saying "OMG DEADLOCK" etc. Which is basically just misinformation.

ProTip: Usually when you give an example to a person, you use a situation that is both relevant and correct.

Also, based on your example, that "thing" not updating because

Originally Posted by Vlada

Those cant detect deadlocks.

implies that when they don't update it is from, you guessed it, a deadlock. So by that reasoning, that "thing" not updating due to a deadlock would be DIRECTLY related to the OR code because, you guessed it, its deadlocked.

Simple enough for you? I can dumb it down more if necessary.

[Vlada]

Originally Posted by Lobreeze

Do you even know what you are saying?

blah, blah, blah


blah, blah...

Only person having an issue with this is you.

You don't understand or don't want to understand, it makes no difference anyway. Personally i think your just bored.

Anyway, we dragged this thread off topic enough as it is. Sorry about that Dame.