• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            天行健 君子當(dāng)自強(qiáng)而不息

            Getting Online with Multiplayer Gaming(11)

             

            The Message Queue

            The server never deals directly with incoming messages; instead, the server pulls
            messages from the queue. If a message needs to be processed, it must be inserted
            into the queue. Using a queue ensures that the server never gets bogged down with
            processing incoming network data.

            The queue is just an array of sMsg structures that is allocated when the application
            class is initialized. I set a limit of 1,024 messages to be allocated for the server, but you
            can change that amount just by altering the MAX_MESSAGE macro in the source code.

            To track messages being added and removed from the queue, use two variables—
            m_msg_head and m_msg_tail. Check out Figure 19.12 to see how the queue uses those
            two variables to track which messages are to be inserted or removed.

            Whenever a message needs to be added to the message queue, a special function is
            called. That function is cApp::queue_msg, and it takes a single argument: the
            sMsg structure to add to the queue.

            Remember the incoming message functions of cApp (covered in the section “DirectPlay
            Messages to Game Messages”)? Those functions built a message structure and added
            the message to the queue via queue_msg. Look at the queue_msg code to see what’s
            going on:

            bool cApp::queue_msg(const void* msg)
            {
                
            const sMsgHeader* header = (const sMsgHeader*) msg;

                
            // return if no room left in queue
                if((m_msg_head + 1) % MAX_MESSAGES == m_msg_tail)
                    
            return false;

                
            // stuff message into queue
                if(header->size <= sizeof(sMsg))
                {
                    EnterCriticalSection(&m_msg_cs);

                    memcpy(&m_msgs[m_msg_head], msg, header->size);

                    
            // goto next empty message (flip around if at end)
                    m_msg_head++;

                    
            if(m_msg_head >= MAX_MESSAGES)
                        m_msg_head = 0;

                    LeaveCriticalSection(&m_msg_cs);
                }

                
            return true;
            }

            As you can see, queue_msg merely copies the supplied sMsg structure into the
            next available element in the message array (pointed to by m_msg_head). Two things
            you haven’t seen are the EnterCriticalSection and LeaveCriticalSection functions.
            Windows uses these two functions to restrict the application’s access to memory
            (using the EnterCriticalSection function), only allowing a single process to modify
            that memory. Once you finish modifying the memory, you need to inform
            Windows by calling LeaveCriticalSection.

            Although this may not make sense at first, think about it like this—the network
            component (a process) is running in the background at the same time as the application
            (another process). If the network component is adding messages to the
            array while the application is trying to remove messages or modify the messages,
            the program data can become corrupt. Critical sections ensure that only one
            process gets sole access to data for a short time.

            posted on 2007-12-18 21:25 lovedday 閱讀(167) 評(píng)論(0)  編輯 收藏 引用


            只有注冊(cè)用戶(hù)登錄后才能發(fā)表評(píng)論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問(wèn)   Chat2DB   管理


            公告

            導(dǎo)航

            統(tǒng)計(jì)

            常用鏈接

            隨筆分類(lèi)(178)

            3D游戲編程相關(guān)鏈接

            搜索

            最新評(píng)論

            久久久久久午夜精品| 高清免费久久午夜精品| 久久亚洲国产午夜精品理论片| 精品久久久久久国产| 一本色道久久综合狠狠躁篇| 久久精品国产亚洲精品| 无码任你躁久久久久久久| 最新久久免费视频| 久久亚洲精品无码播放| 久久最新免费视频| 亚洲国产精品综合久久一线 | 亚洲人AV永久一区二区三区久久| 久久国产乱子伦精品免费午夜| 久久国产精品国语对白| 亚洲精品美女久久久久99小说 | 久久99久久99精品免视看动漫| 中文字幕无码久久人妻| 亚洲午夜久久久久妓女影院| 久久99精品久久久久久hb无码 | 久久久一本精品99久久精品88| 少妇无套内谢久久久久| 精品无码久久久久久午夜| 99久久综合狠狠综合久久| 午夜福利91久久福利| 久久婷婷五月综合色奶水99啪| 天天久久狠狠色综合| 久久夜色精品国产亚洲| 免费国产99久久久香蕉| 思思久久好好热精品国产| 成人综合伊人五月婷久久| 亚洲综合久久夜AV | 久久青草国产手机看片福利盒子| 亚洲精品第一综合99久久| 久久免费精品视频| 亚洲综合精品香蕉久久网| 国产99久久九九精品无码| 亚洲中文字幕久久精品无码喷水| 精品国产91久久久久久久a| 久久亚洲精品国产精品| 国产精品久久久久久久人人看| 久久免费高清视频|