• <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.¢%

            像打了激速一樣,以四倍的速度運轉(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
            99久久综合国产精品免费| 国产产无码乱码精品久久鸭| 国产激情久久久久影院小草 | 狠狠色婷婷久久一区二区| 亚洲午夜久久久久久噜噜噜| 亚洲国产精品久久久久| 性做久久久久久久久| 国内精品伊人久久久久| 亚洲色欲久久久综合网| 久久综合九色综合久99| 久久人人爽人人人人片av| 国产精品成人精品久久久| 久久久精品国产sm调教网站| 亚洲人成网站999久久久综合| 精品亚洲综合久久中文字幕| 久久热这里只有精品在线观看| 国产99精品久久| 新狼窝色AV性久久久久久| 四虎影视久久久免费观看| 久久国产精品-国产精品| 久久影院综合精品| 久久精品视频一| 久久婷婷国产剧情内射白浆| 久久99精品免费一区二区| 亚洲综合婷婷久久| 精品久久久久久久| av无码久久久久不卡免费网站 | 欧美日韩成人精品久久久免费看| 99久久精品国产麻豆| 亚洲第一极品精品无码久久| 亚洲一区精品伊人久久伊人| 国内精品久久久人妻中文字幕| 成人综合伊人五月婷久久| 一级做a爰片久久毛片免费陪| 久久精品国产99久久丝袜| 久久综合伊人77777麻豆| 国产精品九九久久精品女同亚洲欧美日韩综合区 | 成人资源影音先锋久久资源网| 99久久人妻无码精品系列蜜桃| 久久久无码精品亚洲日韩蜜臀浪潮 | 日本免费一区二区久久人人澡|