• <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
            久久综合视频网站| 亚洲国产高清精品线久久| 久久亚洲2019中文字幕| 超级碰久久免费公开视频| 久久亚洲欧美国产精品| 无码人妻久久一区二区三区免费 | 国产成人精品综合久久久| 久久久综合香蕉尹人综合网| 香港aa三级久久三级| 亚洲一本综合久久| 精品久久久久一区二区三区 | 久久久精品久久久久影院| 亚洲午夜福利精品久久| 日产精品久久久久久久| 成人国内精品久久久久影院| 精品久久人人做人人爽综合| 亚洲国产精品无码久久九九| 精品国产一区二区三区久久久狼 | 久久亚洲美女精品国产精品| 久久99精品国产| 亚洲午夜无码AV毛片久久| 国产精品久久成人影院| 日本精品久久久久久久久免费| 亚洲成色www久久网站夜月| 久久精品无码免费不卡| 久久久久亚洲AV无码永不| 久久久这里有精品| 色婷婷狠狠久久综合五月| 精品久久久久中文字幕一区| 久久久久久毛片免费播放| 国产成人久久精品一区二区三区| 久久91精品综合国产首页| 久久―日本道色综合久久| 久久久久国产一级毛片高清版| 久久精品国产亚洲AV无码娇色| 久久成人国产精品免费软件| 久久这里有精品| 蜜臀久久99精品久久久久久小说| 久久精品成人欧美大片| 狠狠色婷婷久久综合频道日韩 | 久久久久九九精品影院|