Changeset 232 for trunk/src/game/WorldSocket.h

Timestamp:

11/19/08 13:48:57 (17 years ago)

Author:

yumileroy

Message:

[svn] *** Source: MaNGOS ***
* Fixed english spelling in src/game/WorldSocket.h/cpp. Author: Derex
* [240_world.sql] Create new command .senditems and remove from moderator level command .sendmail possibility send items. Author: Vladimir
* Added new command: .sendmoney player "subject" "message" money - Sends a mail with money to a player. Author: fredi
* Correctly apply taken damage debufs/bonuses in cases non-physical melee damage. Author: Frankir
* Fix a crash in add friend/ignore callback. (check if player still logged in). Author: Hunuza
* Better args checking in .sendmoney command. Author: Vladimir

Original author: visagalis
Date: 2008-11-14 17:50:48-06:00

Files:

• trunk/src/game/WorldSocket.h (modified) (6 diffs)

trunk/src/game/WorldSocket.h

@@ -56 +56 @@
  * WorldSocket.
  *
- * This class is responsible for the comunication with
+ * This class is responsible for the communication with
  * remote clients.
  * Most methods return -1 on failure.
- * The class uses refferece counting.
+ * The class uses reference counting.
  *
  * For output the class uses one buffer (64K usually) and
  * a queue where it stores packet if there is no place on
  * the queue. The reason this is done, is because the server
- * does realy a lot of small-size writes to it, and it doesn't
+ * does really a lot of small-size writes to it, and it doesn't
  * scale well to allocate memory for every. When something is
- * writen to the output buffer the socket is not immideately
+ * written to the output buffer the socket is not immediately
  * activated for output (again for the same reason), there
  * is 10ms celling (thats why there is Update() method).
- * This concept is simmilar to TCP_CORK, but TCP_CORK
- * usses 200ms celling. As result overhead generated by
+ * This concept is similar to TCP_CORK, but TCP_CORK
+ * uses 200ms celling. As result overhead generated by
  * sending packets from "producer" threads is minimal,
- * and doing a lot of writes with small size is tollerated.
- *
- * The calls to Upate () method are managed by WorldSocketMgr
+ * and doing a lot of writes with small size is tolerated.
+ *
+ * The calls to Update () method are managed by WorldSocketMgr
  * and ReactorRunnable.
  *
  * For input ,the class uses one 1024 bytes buffer on stack
- * to which it does recv() calls. And then recieved data is
- * distributed where its needed. 1024 matches pritey well the
+ * to which it does recv() calls. And then received data is
+ * distributed where its needed. 1024 matches pretty well the
  * traffic generated by client for now.
  *
  * The input/output do speculative reads/writes (AKA it tryes
- * to read all data avaible in the kernel buffer or tryes to
- * write everything avaible in userspace buffer),
- * which is ok for using with Level and Edge Trigered IO
+ * to read all data available in the kernel buffer or tryes to
+ * write everything available in userspace buffer),
+ * which is ok for using with Level and Edge Triggered IO
  * notification.
  *
@@ -100 +100 @@
         typedef ACE_Acceptor< WorldSocket, ACE_SOCK_ACCEPTOR > Acceptor;
 
-        /// Mutex type used for various syncronizations.
+        /// Mutex type used for various synchronizations.
         typedef ACE_Thread_Mutex LockType;
         typedef ACE_Guard<LockType> GuardType;
@@ -121 +121 @@
         int SendPacket (const WorldPacket& pct);
 
-        /// Add refference to this object.
+        /// Add reference to this object.
         long AddReference (void);
 
-        /// Remove refference to this object.
+        /// Remove reference to this object.
         long RemoveReference (void);
 
@@ -186 +186 @@
         ACE_Time_Value m_LastPingTime;
 
-        /// Keep track of overspeed pings ,to prevent ping flood.
+        /// Keep track of over-speed pings ,to prevent ping flood.
         uint32 m_OverSpeedPings;
 
@@ -198 +198 @@
         LockType m_SessionLock;
 
-        /// Session to which recieved packets are routed
+        /// Session to which received packets are routed
         WorldSession* m_Session;
 
-        /// here are stored the fragmens of the recieved data
+        /// here are stored the fragments of the received data
         WorldPacket* m_RecvWPct;
 
         /// This block actually refers to m_RecvWPct contents,
-        /// which alows easy and safe writing to it.
+        /// which allows easy and safe writing to it.
         /// It wont free memory when its deleted. m_RecvWPct takes care of freeing.
         ACE_Message_Block m_RecvPct;
 
-        /// Fragment of the recieved header.
+        /// Fragment of the received header.
         ACE_Message_Block m_Header;
 
-        /// Mutex for protecting otuput related data.
+        /// Mutex for protecting output related data.
         LockType m_OutBufferLock;
 
@@ -222 +222 @@
 
         /// Here are stored packets for which there was no space on m_OutBuffer,
-        /// this alows not-to kick player if its buffer is overflowed.
+        /// this allows not-to kick player if its buffer is overflowed.
         PacketQueueT m_PacketQueue;