Slashdot Mirror

← Back to Stories (view on slashdot.org)

Rendezvous For Apache

Posted by pudge on from the next-up-is-zeroclick dept.

sapporo writes "Eric Christopher Seidel has released mod_rendezvous. The DSO lets the Apache that comes with Mac OS X advertise its services on the local network via Rendezvous, so it will show up in Safari's Rendezvous Bookmarks section. This lets you browse all web servers on the local network very conveniently. Nice one!" I wonder, could it work on Linux too? I would think so ...

4 of 44 comments (clear)

  1. Very nice idea by Matthias+Wiesmann · · Score: 4, Insightful
    I was also suprised that Apple did not activate this for personal web sharing. It is nice that somebody corrected it. This said, in my case, the hack does not work correctly: it seems the advertised local address has a period after the .local domain, so the browser can't find the actual web server.

    I really hope that rendez-vous technologies get ported to other Unixes soon. For instance, multicast DNS is really nice in LANs where IP addresses are assigned via DHCP. You can simply type something like ssh server.local and it works. When you use laptops, it is really a killer feature.

  2. Re:Not really open sourced by entrylevel · · Score: 3, Insightful

    When I went to the site (2 days ago), there was a note that said 'If you want the source, e-mail me and I'll send it to you.' Perhaps he didn't think too many people would be interested, or has limited webspace.

    --
    Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
  3. Re:interesting... by Twirlip+of+the+Mists · · Score: 5, Insightful

    Take the Safari browser for example, David Hyatt is actually responding to other people's blogs about Safari and actually taking notice.

    If by "actually taking notice" you mean "fixing reported bugs left and right," you're right. Hyatt's team is doing some incredible stuff. They're just chewing through bug reports.

    I've emailed David asking if they plan to put WebCore and JavaScriptCore on the public CVS server so we can test newer builds. No answer yet, but I'll bet I get a "yes" back soon.

    --

    I write in my journal
  4. Not the same thing by Matthias+Wiesmann · · Score: 3, Insightful
    While the basic functionality is similar, both approaches are quite different and quite complimentary. Dynamic DNS makes sense for servers that need to be reachable from the whole internet.

    Dynamic DNS makes little sense if somebody plugs-in a laptop in a LAN. You don't want to update your DNS data to include a laptop that might stay connected for a few minutes! There are also administrative issues: DNS updates will certainly not be allowed for arbitrary machines or arbitrary DNS names.

    Multicast DNS solves this problem nicely and even works when you don't have a server. So if a friend plugs a laptop in your home network you can address his machine using a logical name.

    Different problems, different solutions...