re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
CodeDragon
I wouldn't hardcode 127.0.0.1 in as a valid mus socket ip, you never know if there is a shell uploaded to the server or someone has access to the server and uploads some sort of tool. These are potentially threads but will less likely happen.
Also, you've made a interface folder while you put abstract or internal classes in there, this is a bit confusing since interfaces aren't the same as an abstract class. An internal class can only be used by the same project and will not go outside of the project. This is not an interface.
Well, if someome uploads a shell they could just rank theirself, acces the whole db and stuff, so mus wouldnt be so bad
Verzonden vanaf mijn iPhone met Tapatalk
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
ImNotSatan
Well, if someome uploads a shell they could just rank theirself, acces the whole db and stuff, so mus wouldnt be so bad
That's just an excuse for making it not be so bad, there are many case senarios that you don't want to have it open for 127.0.0.1. I just want to point out that he should make this fully configurable for everyone, I know he is adding it to prevent noobs from screwing up.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
CodeDragon
That's just an excuse for making it not be so bad, there are many case senarios that you don't want to have it open for 127.0.0.1. I just want to point out that he should make this fully configurable for everyone, I know he is adding it to prevent noobs from screwing up.
Well to be honst i never knew this emu had mus
(Never needed it so yeah)
Should be configureable yeah thatll be quite nice for like special staff clients
Verzonden vanaf mijn iPhone met Tapatalk
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
CodeDragon
I wouldn't hardcode 127.0.0.1 in as a valid mus socket ip, you never know if there is a shell uploaded to the server or someone has access to the server and uploads some sort of tool. These are potentially threads but will less likely happen.
Also, you've made a interface folder while you put abstract or internal classes in there, this is a bit confusing since interfaces aren't the same as an abstract class. An internal class can only be used by the same project and will not go outside of the project. This is not an interface.
Yeah, but i didn't finished the PSR writing. I only separated some things in other folders to avoid these MIX.
But i will redo the folder structure.
MUS isn't coded in Yupi. i forgot removing the configuration settings of mus in config file.
- - - Updated - - -
Commited to Yupi.
See changes in OP.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
ovflowd
Commited to Yupi.
Could you atleast say what you've updated? Your threads (this one and the one in the release section) are bumped daily with the same message.
It'd gave more value if you actually said what you've updated.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
The General
Could you atleast say what you've updated? Your threads (this one and the one in the release section) are bumped daily with the same message.
It'd gave more value if you actually said what you've updated.
I'm putting commit details in this Post: http://forum.ragezone.com/f331/yupi-...5/#post8545795 (#3)
- - - Updated - - -
Reason of changing the base of Asynchronous File Appender from RollingFileAppender to FileAppender:
1. As the emulator have multiple threads, RollingAppender only allows one open instance of file stream, locking the file. When other thread/void from the Emulator call's the Log Manager, the Lock is endless, waiting the first stream close (only on Log Manager Dispose).
2. So changed to Normal File Appender, using Asynchronous creating a Queue with the Errors, dumping they only on Emulator Shutdown.
This is good because we don't want a stream opening every time in Emulator Execution, opening stream for append text in the file increase the pause of thread execution, increasing the chances of some thread crashing.
3. Also is good put the logs only in shutdown because to fix any error you need edit source code and shut down emulator.
That was a noob-friendly explain and really condensed.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Its time to fix the known issues :)
and then MUS Socket adding !!
:DDD im so excited
@ovflowd
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
OP, when updating thread, instead of sending "commited again", I request for you to add what have you commited, unless it's only bump and post count.
Tell what you have updated. Even though, I know that you're updating the changelog post ( http://forum.ragezone.com/f331/yupi-...5/#post8545795 ) it would be for the better interest from the people around to know what are you doing at the moment instead of only bumping it.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
@ovflowd
claudio, the time is coming to fix the known issues.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Juice, first stability, later features. I have a life '-'
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
ovflowd
Juice, first stability, later features. I have a life '-'
You have do commits over 10 times for the performance.-___-Its time now
Yupi! - C# 6 Rosylin - MySQL / Based on old Azure Emulator
Quote:
Originally Posted by
Juicex3
You have do commits over 10 times for the performance.-___-Its time now
Calm ur tits
It will be done by time
The stability is more important than the bugs atm
Verzonden vanaf mijn iPhone met Tapatalk
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Commited. Adding Commit Log in few min.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]