i really look forward to this server.
Goodluck with this project hope you race your own roads :P
i really look forward to this server.
Goodluck with this project hope you race your own roads :P
https://github.com/CrowleyCrossroads...neFactory.java
You need add Executor to your pipeline or you block the worker thread which is not good. Check out Netty OrderedMemoryAwareThreadPoolExecutor
Just pushed the latest code to Github, username's are now validated using a regex and "{MOD,ADM,SOS}-" are blocked in usernames (i'll test if the name is in use at some point). Passwords are also validated >5 chars and 10< and you must use numbers. Email validation is implemented using a regex but the client doesn't seem to like the message *shrug*
Why not just send it through a method, if it contains a "@" and a valid website organisation extension? :DOriginally Posted by Crossroads
How would that change the clients acceptance of the message? Its just a Boolean response... And I would rather use a regex that conforms to the RFC specification so that all TLDs are supported.
Any updates? Looks really promising :D
Pushed to GitHub, user names are now checked against the database to see of it is in use. I'm aware it currently blOcks the event thread I'll move it to a threadpool at some point.
Moved database logic into an ExecutorService so it doesn't block the event thread an I'm goin to move all OutgoingMessages into a similar format.
Three days since last update. Any more?
Fixed an issue with logging, that caused massive logfiles to be generated still trying to get the ParentalConsent message to work though and the Encoder now displays the correct session ID for outgoing messages.
Tried to bypass the ParentalConsent message by sending the response early inside the EmailValidator (CY1\01) however it doesn't seem to work.
I've noticed some of the issues that he's having I've sent him a message on Skype, preparing for college now, whenever he logs in he should get em ;p
Outgoing messages will run on the same thread that processed the incoming using the Executor thread provided in the Netty Pipeline. That is of course if you are sending back the response in the Message.
You will just be passing from one thread to another, which has its good and bads, but it isn't really necessary.
Id say experiment and see whats best.
Good job btw
I've been busy the last few days, i should be able to work on this again early next week i'm currently busy with work.
It's a shame this project is so under rated. Looks awesome.
Sounds awesome, good luck!
