I just started using SmartFox, so here are the things that came up out of the box for me. In general I've had a very good experience with SmartFox server and look forward to using it further.
Logging Services - You have a full logging implementation, why not extend the trace() functionality to support standard multiple logger levels and provide each extension with its own log file. It would keep the console log free of debug clutter and the like.
Custom Admin Statistics - In the admin console, the extensions view should have a column for custom statistics. A reasonably complex extension will have custom statistics that would be nice to present through the admin console. This could be as simple as an array of room variables for the admin client and a UI update.
JMX style management of extensions - It would be nice to have some way to make calls to control complex extensions. This could be as simple as defining an internal event that can be fired from the admin console (perhaps you just define what events the admin user can fire in config.xml then provide a generic interface to fire such events from the admin console).
Graceful login failure - When you call the login function of the client API and pass it a zone that does not exist it hangs (no error event is sent). While this would typically be a simple code bug that will not show up in production, there is potential that a zone might be unloaded or the server mis-configured and clients will not receive a graceful error message (and the developer also has no way to receive the error message and take further action to notify the administrators directly from the client).
4 things: Logging, statistics, JMX, graceful login error
-
davidparks21
- Posts: 14
- Joined: 31 Jul 2009, 07:48
Hi there,
nice suggestions, a good percentage is in the works for the next major release
Some additional comments from our perspective:
You can optionally set the <WarnOnWrongZoneRequest> tag in the config.xml
More details in the release notes: http://www.smartfoxserver.com/products/ ... 1_6_6.html
greetings
nice suggestions, a good percentage is in the works for the next major release
Some additional comments from our perspective:
This is interesting although having many different log files open is going to impact the performance significantly.You have a full logging implementation, why not extend the trace() functionality to support standard multiple logger levels and provide each extension with its own log file. It would keep the console log free of debug clutter and the like.
JMX is very likely to be integrated in the next major release.JMX style management of extensions
This was already implemented in version 1.6.6Graceful login failure -
You can optionally set the <WarnOnWrongZoneRequest> tag in the config.xml
More details in the release notes: http://www.smartfoxserver.com/products/ ... 1_6_6.html
greetings
-
davidparks21
- Posts: 14
- Joined: 31 Jul 2009, 07:48
My suggestion on Log Files then is to make no more than 1 log file per Zone rather than per extension, and enable them in the config file (default the logging sevice to off). Provide a config file option to automatically log the extension it came from (some thing like [date ext_name]: <log_msg>)
Regarding the warn on wrong zone - great to see it's implemented. I'm curious to know why it's recommended to keep off in production.
Otherwise, great to hear that a lot of this is on the drawing board already. This is a great product you've put together!
David
Regarding the warn on wrong zone - great to see it's implemented. I'm curious to know why it's recommended to keep off in production.
Otherwise, great to hear that a lot of this is on the drawing board already. This is a great product you've put together!
David