Code Monkey home page Code Monkey logo

Comments (6)

roehling avatar roehling commented on May 31, 2024

Since the daemon is supposed to listen to loopback only, I don't think we really need dual stack support. In fact, the only reason I added IPv6 support in the first place was to ensure that the daemon can run on IPv6-only hosts.

from postsrsd.

quanah avatar quanah commented on May 31, 2024

I disagree. ;) The OS may prefer to attempt connecting to the ipv6 addr over the ipv4 addr when supporting both ipv4 & ipv6, so listening on ipv6 can save a few milliseconds every time a new connection is opened, which adds up over time. Particularly if setting something like: tcp:localhost:10001

from postsrsd.

bjoe2k4 avatar bjoe2k4 commented on May 31, 2024

Quick solution if you really wanna have dualstack right now: modify the start script to start postsrsd twice (or duplicate the init script). The overhead is really minimal.

On the other hand a typical latency of an email messages is in the order of seconds to minutes (depending on the antispam mechanisms) and i don't think a few microseconds matter in this case.

from postsrsd.

quanah avatar quanah commented on May 31, 2024

My use case is probably not the same as most peoples. I'm working at integrating postSRSd into our product, which is used by clients who may have 10 users or 150 million + users. Efficiency matters significantly in this case. So does the ability to easily automate the installation and configuration, and to honor what the client specifies as to how they want things to behave (ipv4 only, dual, or ipv6 only). Then there are other issues, such as the broken version of netcat shipped in RHEL7, which if you're using it to test ports being alive, doesn't work right if it an interface has both ipv6 and ipv4 enabled, because it won't fail over to the ipv4 address. So in this case, if I were to try and validate a response from postsrsd, it would fail on rhel7 with 127.0.0.1 and ::1 being active.

from postsrsd.

roehling avatar roehling commented on May 31, 2024

I will see what I can do. Thankfully, Postfix keeps the TCP connection alive (and PostSRSd supports that), so the actual connection overhead is almost nonexistent on a busy system.

from postsrsd.

quanah avatar quanah commented on May 31, 2024

Thanks, I appreciate it!

from postsrsd.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.