• <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>

            S.l.e!ep.¢%

            像打了激速一樣,以四倍的速度運(yùn)轉(zhuǎn),開心的工作
            簡單、開放、平等的公司文化;尊重個性、自由與個人價值;
            posts - 1098, comments - 335, trackbacks - 0, articles - 1
              C++博客 :: 首頁 :: 新隨筆 :: 聯(lián)系 :: 聚合  :: 管理

            源URL:http://lists.zeromq.org/pipermail/zeromq-dev/2010-February/002383.html

            意思沒太懂,大概就是Z.E.R.O.M.Q主要是針對服務(wù)器間的通信,獲取客戶端連接IP的意義不大

            Hi Fred,
            
            >>> Just one question remains : were can I grab in the server
            >>> environment the IP address and portnumber of the sending client ?
            >> No way to do that at the moment, other than doing it at the app level
            >> (make up a client ID / use the IP address and stick it in the
            >> message).
            
            Let me give some background here.
            
            Simply said: 0MQ should manage connections for you. Your application 
            should be agnostic about exact location/identity of the peers. If you 
            want to work on the level of individual connections, use BSD sockets 
            rather than 0MQ.
            
            More complex answer: The issue has to do with scaling 0MQ into internet 
            scales. What you want to know is the identity of the peer who sent the 
            message. You are not interested in any middleboxes that may be on the 
            way (like zmq_forwarder etc.) Thus, getting IP address we've received 
            the message from is useless - it's IP address of the previous hop. Also, 
            if IP address is used as the identity, two applications running on the 
            same box would look exactly the same. Same application bound to several 
            network interfaces would look different depending on how exactly you are 
            connected to it. Etc.
            
            At the moment, the only thing you can do is to choose a name for your 
            application and fill it into the message. In easy to modify 0MQ to do 
            the thing for you, however, it's not a conceptual solution.
            
            Real solution still requires a lot of research work. Feel free to start 
            the discussion though.
            
            > OK, but that's (at least for me) not thrustworthy. Like SMTP telling me 
            > who they are. ;-)
            
            What you would consider trustworthy, what kind of attacks should it be 
            resistent to, etc.
            
            > You don't mind if I take a look at the sources to see whether it is 
            > doable for me ?
            
            Sure. Go for it. Any experimentation is valuable! The source is licensed 
            under LGPL so you can modify it in any way given that you publish the 
            result under LGPL.
            
            Martin

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


            人人狠狠综合久久亚洲| AV无码久久久久不卡蜜桃| 久久久久久综合一区中文字幕| 久久99国产亚洲高清观看首页| 亚洲精品视频久久久| 亚洲国产另类久久久精品小说| 久久996热精品xxxx| 人妻无码αv中文字幕久久| 精品久久久久一区二区三区| 中文字幕久久久久人妻| 久久精品中文字幕第23页| 91精品国产高清91久久久久久| 亚洲精品成人久久久| 久久九九青青国产精品| 亚洲精品美女久久久久99| 久久无码一区二区三区少妇 | 久久毛片一区二区| 久久噜噜电影你懂的| 久久精品人人做人人爽电影蜜月| 久久精品国产WWW456C0M| 色噜噜狠狠先锋影音久久| 久久人人爽人人爽人人爽| 日韩精品无码久久一区二区三| 久久99热国产这有精品| 97久久超碰国产精品旧版| 伊人久久大香线蕉综合影院首页| 中文国产成人精品久久亚洲精品AⅤ无码精品 | 一级做a爰片久久毛片毛片| 国产91久久综合| 91精品国产色综久久| 久久国产一区二区| 亚洲国产成人久久综合一| 老司机国内精品久久久久| 久久久久国产一级毛片高清版| 国产精品久久久久久| 99久久亚洲综合精品成人| 国产成人精品久久亚洲高清不卡 | 久久国产精品99久久久久久老狼| 99久久精品国产高清一区二区| 狠狠狠色丁香婷婷综合久久五月| 精品综合久久久久久888蜜芽|