• <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),開心的工作
            簡單、開放、平等的公司文化;尊重個(gè)性、自由與個(gè)人價(jià)值;
            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主要是針對(duì)服務(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ā)表評(píng)論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問   Chat2DB   管理


            97精品依人久久久大香线蕉97| 成人精品一区二区久久| 久久久无码精品午夜| 久久天天躁狠狠躁夜夜不卡| 一本一本久久A久久综合精品| 久久久精品人妻一区二区三区蜜桃 | 少妇久久久久久被弄到高潮| 99精品久久久久久久婷婷| 韩国免费A级毛片久久| 三级片免费观看久久| 99久久99这里只有免费费精品| 精品久久久久久无码人妻热| 无码人妻久久一区二区三区免费 | 国产精品久久久99| 久久久久国产精品熟女影院 | 丁香久久婷婷国产午夜视频| 久久综合九色综合网站| 麻豆精品久久精品色综合| 亚洲精品tv久久久久| 99国内精品久久久久久久| 久久人人爽人人爽人人片av麻烦| 亚洲国产精品一区二区久久| 久久久久亚洲av无码专区导航| 久久久久亚洲精品天堂久久久久久| 色欲综合久久躁天天躁蜜桃| 伊人久久大香线蕉亚洲五月天| 亚洲精品国产综合久久一线| 久久久久成人精品无码| 成人国内精品久久久久影院VR| 久久久久高潮毛片免费全部播放| 久久久久亚洲AV无码观看| 久久精品国产只有精品66| 99久久免费只有精品国产| 国产精品一久久香蕉产线看| 浪潮AV色综合久久天堂| 无码专区久久综合久中文字幕| 久久这里只有精品视频99| 狠狠久久综合伊人不卡| 国产精品VIDEOSSEX久久发布| 四虎国产永久免费久久| 久久久久久久久无码精品亚洲日韩 |