Zone : Specify the combination of rooms and extensions. In other words we can say that the for one application or game generally we define one zone.
Extensions : These are the server side file which we use for the application.
Archive for the ‘Server Side Config’ Category
SmartFoxServer Chapter 12 – server side config –part-9
October 10th, 2010 by admin | 2 Comments | Filed in Server Side Config, SmartFox ServerSmartFoxServer Chapter 11 – server side config –part-8
October 10th, 2010 by admin | No Comments | Filed in Server Side Config, SmartFox Server
Active : It is a Boolean value. By selecting true/false we can on/off webserver.
CfgFile: It shows the location of http server config file.
SmartFoxServer Chapter 10 – server side config –part-7
October 10th, 2010 by admin | 2 Comments | Filed in Server Side Config, SmartFox ServerAutoReloadExtensions : It is a Boolean value . By using it we can enable/disable the
auto-reload feature for extensions. For example the server will reload extensions
as soon as they are modified.
IpFilter : Â Here we specify the number of users that can be created by one single IP Address.
Mailer : Here we can set the email. The required thing is valid SMTP account.
MailHost :Â Here we specify the SMTP IP address or host name.
MailUser : Here we specify the SMTP username.
MailPass : Here we specify password.
SmtpPort: Here we specify the SMTP port number.
EnableZoneInfo : It is Boolean value . using feature Enable / disable we can know how many clients are connected through the server currently.
SmartFoxServer Chapter 8 – server side config –part-5
October 10th, 2010 by admin | 3 Comments | Filed in Server Side Config, SmartFox Serverlets move forward with the config :
ClientMessagQueue:
Sometimes network doesn’t work in fill speed and not always permit to send the messages in fast speed at the same rate of messages are produced on the server side. In that case SmartFoxServer creates a queue of outgoing message packets that should be sent to the user.
Â
QueueSize : Here we specify the size of queue .
MaxAllowedDroppedPackets : Here we specify the amount of dropped messages that can be tolerated
MaxIncomingQueue : Here we specify the maximum number of  requests that can be enqueued by the server. By default it is 8000.
DeadChannelsPolicy : Here we specify the server policy for dead / closed socket channels.
There are two modes are available:
normal: allows unexpectedly closed or stalled socket connections to live longer in memory.
strict: this is recommended . It  uses a more efficient way to catch unexpected disconnections or closed channels. Immediately gets rid of closed channels, releasing their resources.
MaxMsgLen :Maximum length of message.
LogMaxSize : Maximum size of  each log file .
LogMaxFile:Maximum number of file log files which can be created from the server.
Next Chapter
Tags: ClientMessagQueue, config, DeadChannelsPolicy, dropped messages, length of message, LogMaxFile, LogMaxSize, MaxAllowedDroppedPackets, MaxIncomingQueue, MaxMsgLen, QueueSize, server, tolerated
Smartfox Server–Chapter 07-Server side Config-part-4
October 3rd, 2010 by admin | No Comments | Filed in Server Side Config, SmartFox Server————————————————————————————————-
Server side Config-part-4
————————————————————————————————-
Lets continue with following tags :
BanCleaning : here we can set it auto. In a specific interval which BanDuration it will clean the ban.
BanDuration: here we can set the duration of ban.
BannedLoginMessage : Here we can set the cutom message for the banned user.
OutQueueThreads: This tag is basically used as the performance settings. It represents the number of Java worker threads used for the SmartFoxServer EventWriter. The EventWriter is the server stage responsible for broadcasting messages back to the connected clients and it is usually one of the most busy stages of the server. By default it is assigned 1 thread . We generally use (number of cpus / 2) rule to decide how many threads to assign .
ExtHandlerThreads: Here we can set the size of the thread pool. By default it is 1. Only in special case like when one extension blocks for a certain amount of time waiting for a resource, an external response or a complex database request etc we need to increase it.
MaxWriterQueue: The maximum number of messages that can be added to the outgoing message queue. This parameter is already set by default to a high value.
Tags: (number of cpus / 2) rule, BanCleaning, BanDuration, banned user, BannedLoginMessage, broadcasting, complex database request, connected clients, default to a high value, EventWriter, extension blocks, external response, ExtHandlerThreads, increase, Java worker threads, MaxWriterQueue, outgoing message queue, OutQueueThreads, performance settings, resource, Server side Config, server stage, SmartFoxServer EventWriter, tags, The maximum number of messages, thread pool
Smartfox Server–Chapter 06-Server side Config-part-3
October 3rd, 2010 by admin | No Comments | Filed in Server Side Config, SmartFox Server————————————————————————————————————————-
Server side Config-part-3 Bad words filtering
————————————————————————————————————————-
Lets continue with Bad words filtering  
SmartFoxServer provides a built-in customizable bad words filter which allow automatic moderation of chat applications and games. We can make a list of bad words that we want to be filtered and server will automatically handle that by replacing them with asterisks or completely remove the phrase.
Also you can turn automatic administrator messages and specify the amount of warnings before the user is kicked and the amounts of kicks before the user is completely banned from the server.
Active : It is a Boolean value which specify if we want to use this feature.
FilterMode : There are two mode :
a). FILTER : It will replace the bad words with asterisks
b). REMOVE : it will remove every phrase containing bad words
StripCharacters : By default the following characters are , . ; : _ ! $ % & / # * – +.By using this feature we can specify which characters should be stripped from the original message
Warnings: It is a Boolean value. By turning them on the server will send a custom warning message to the user each time a bad word is detected or removed.
FilterRoomNames : It is a Boolean value. By turning them on it will filter bad words in room names.
FilterUserNames: It is a Boolean value. By turning them on it will filter bad words in user nicknames.
WarningsBeforeKick: Here we can specify how many warnings are sent before the user is automatically kicked.
WarningMessage : Here we can specify the custom warning message.
KickMessage : Here we can specify the custom kick message.
BanMessage: Here we can specify the custom ban message.
BanAfter: Here we can specify how many kicks are tolerated before the user is automatically banned from the server.
BadWordsList : Here we can list the custom list of bad words to be filtered.
Tags: Active, administrator messages, asterisks, automatic moderation, bad word is detected or removed, Bad words filtering, BadWordsList, BanAfter, BanMessage, banned from the server, containing bad words, custom warning message, customizable bad words filter, filter, filtered, FilterMode, FilterRoomNames, FilterUserNames, KickMessage, list of bad words, moderation of chat applications, REMOVE, remove the phrase, Server side Config, StripCharacters, the amount of warnings, the original message, user is kicked, WarningMessage, Warnings, WarningsBeforeKick
Smartfox Server–Chapter 05-Server side Config-part-2
October 3rd, 2010 by admin | No Comments | Filed in Server Side Config, SmartFox Server———————————————————————————————————————
Server side Config-part-2
————————————————————————————————————————
Lets continue with other nodes 
If you want to kick and banish any user you have an automatic option too . SmartFoxServer comes with filter which is called anti-flood filter which allows to automatically kick and banish users that are trying to flood your applications with messages. In above attached image the nodes are divided into sub-nodes lets discuss each node :
AntiFlood active : This is a Boolean value which is use to turn on/off the filter.
MinMsgTime  tolerance : MinMsgTime is the minimum time allowed between two messages. The tolerance attribute stands for the amount of messages. Before sending warning message server will check the tolerance limit.
MaxRepeatedMessages : This is the maximum allowed number of identical messages. After crossing the limit server will automatically send a warning message to user.
WarningsBeforeKick : This is a number value. Where we specify how many warning messages a user can get before being kicked.
WarningMessage : Here we specify the custom message what we want to show as warning message.
KickMessage : Here we specify the custom message what we want to show as kick message.
BanMessage : Here we specify the custom message what we want to show as ban message.
BanAfter This is a number value. Where we specify how many warning messages a user can get before being baned.
Tags: anti-flood filter, AntiFlood active, automatically kick, BanAfter, BanMessage, crossing the limit server, flood your applications, identical messages, kick and banish users, KickMessage, MaxRepeatedMessages, messages, minimum time, MinMsgTime, Server side Config, the amount of messages, The tolerance attribute, tolerance, tolerance limit, warning message server, WarningMessage, WarningsBeforeKick
Smartfox Server – Chapter 04-Server side Config-part-1
October 3rd, 2010 by admin | 1 Comment | Filed in Server Side Config, SmartFox Server———————————————————————————————————-
Server side Config -Part-1
———————————————————————————————————-
Lets discuss now the Server side Config:
Here we can see many nodes in server side config XML . Let me explain each node and its working .
ServerIP : It specify the  IP address of server.
ServerPort : It specify the  Port of server.
AutoSendPolicyFile :  It is a Boolean value .If set to TRUE it allows SmartFoxServer to automatically generate a cross-domain policy file to enable Flash player 7 (7.0.19.0 or later) to connect outside the current domain.  This is used for  those   SWF files  which are  located in different domains.  We often get cross domain error while we try to connect with swf files which are in different domain. To avoid this we need to set it true.
MaxUserIdleTime : The time is expressed in seconds and it represents the maximum time allowed for an idle client. After that time, idle users are automatically disconnected by the server
MaxSocketIdleTime : it comes with the version 1.6.3 .It is an interval of seconds which represents the maximum time a connection can stay idle before the server forces the disconnection. The most important point with this is it is  valid only for client connections that still have to log in the server and create a User session. Once the user is logged in this parameter is ignored and the auto-disconnection will be according to the MaxUserIdleTime parameter.
MaxRoomVars : The maximum number of room variables that can be created in a single room.
MaxUserVars : The maximum number of user variables that can be created by a single user.
UserVarsOptimization : it comes with  the version 1.6.3. It allows to receive only real changes in user variables, avoiding variables that didn’t change to be retransmitted. It helps to improves bandwidth usage when many variables are being used.
Tags: auto-disconnection, automatically disconnected, AutoSendPolicyFile, config XML, cross domain error, cross-domain policy, domains, MaxRoomVars, MaxSocketIdleTime, MaxUserIdleTime, MaxUserIdleTime parameter, MaxUserVars, retransmitted, Server side Config, ServerIP, ServerPort, User session, user variables, UserVarsOptimization
Smartfox server – chapter 03 Client side Config
October 2nd, 2010 by admin | 2 Comments | Filed in Server Side Config, SmartFox ServerSome other nodes of this config.xml :
debug : It is a Boolean value . It holds the client-side debugging information When we set it true , the developer is able to see all server communication with the client in Flash IDE. It helps in debugging during the application development process. Using this we can see the messages in the output window. e.g
blueBoxIpAddress : It is a string value which contains the BlueBox IP address.
blueBoxPort :Â It is a number value contains the Blue box connection port.
smartConnect : It is a Boolean value . By default it is true. Basically it  indicates if the BlueBox http connection should be used in case a socket connection is not available.
httpPort: It is a number value by default it is 8080. This property can be changed according to the webserver’s listening port.
httpPollSpeed :
Here we can specify the  minimum required interval between two polling requests when connecting to SmartFoxServer  via  BlueBox module. The default value is 750 milliseconds. The value should be in betweens  0 and 10000 milliseconds (10 seconds). It adds minimum lag to the client responsiveness and it keeps the server CPU usage low
Optimal Values  for httpPollSpeed:
a). For chats, turn-based games : 750-1000
b). Â For super fast real-time games : 50-100
c)Â Using values below 50 ms is not recommended.
rawProtocolSeparator:Â It is a string value . The default value is “%” . it is used to get or set the character used as separator for the String (raw) protocol
Tags: 750 milliseconds, application development process, BlueBox http connection, BlueBox IP address, blueBoxIpAddress, blueBoxPort, Boolean value, client in Flash IDE, client-side debugging information, connection port, CPU usage, debug, default it is 8080, helps in debugging, httpPollSpeed, httpPort, keeps the server CPU usage low, listening port, minimum lag, minimum required interval, number, Optimal Values, polling, polling requests, property, rawProtocolSeparator, separator for the String, server communication, smartConnect, SmartFoxServer via BlueBox module, socket connection
Follow us on Twitter
Subscribe to our RSS Feeds