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


            中文字幕亚洲综合久久菠萝蜜 | 久久这里只有精品首页| 久久国产精品无码一区二区三区| 日韩精品久久无码人妻中文字幕| 国内精品久久国产大陆| 热久久最新网站获取| 久久精品国产网红主播| 久久国产香蕉视频| 久久久精品人妻一区二区三区四| 精品免费久久久久久久| 久久这里的只有是精品23| 青青草国产精品久久久久| 久久精品国产亚洲7777| 久久国产精品久久国产精品| 久久天天躁狠狠躁夜夜2020| 人妻无码久久一区二区三区免费| 成人国内精品久久久久影院VR| 久久婷婷人人澡人人爽人人爱| 久久精品一区二区国产| 久久天天躁狠狠躁夜夜躁2O2O| 亚洲国产精品成人AV无码久久综合影院| 久久精品午夜一区二区福利| 亚洲国产精品成人久久蜜臀 | 久久精品aⅴ无码中文字字幕不卡| 日本久久中文字幕| 亚洲国产精品久久66| 久久香蕉国产线看观看99| 丁香五月网久久综合| 狠狠88综合久久久久综合网| 午夜精品久久久久久久| 欧美亚洲国产精品久久高清| 色天使久久综合网天天| 久久久久久噜噜精品免费直播| 国产成人精品久久亚洲高清不卡| 久久久久久人妻无码| 久久久精品午夜免费不卡| 久久se精品一区精品二区| 亚洲综合久久综合激情久久| 久久九九亚洲精品| 久久精品二区| 国内精品伊人久久久久妇|