Rendezvous Renamed to OpenTalk

Gogo Dodo writes "Back in August, Slashdot covered Tibco suing Apple over the Rendezvous trademark. AppleInsider now reports that the lawsuit has been settled and Rendezvous' new name will be OpenTalk." Meanwhile Zeroconf sits in the corner and cries.

Comments

More lawsuits to come

[Biotech9]

Apple (and MS) are both being sued over 6 patents held by BTG, which their pnline updating systems allegedly violate.

Link here.

Looks like fun and games ahead for Apples lawyers.

Re:More lawsuits to come

[Orgazmus]

bahagha! pnline isnt a real word! PWND!!

Let me get this straight:

[burgburgburg]

I got this tattoo for nothing?

Okay, this time I mean it: No more product-based body modification.

Re:Let me get this straight:

[System.out.println()]

Sad, but true....

now

[TexasDex]

Cue "Lindevous" jokes.

Bad Choice

[Johnny Mozzarella]

Sounds too much like AppleTalk.
I can hear the IT folks gripping.

Re:Bad Choice

[Rosyna]

Well, maybe you don't realize this, but Rendezvous basically *is* AppleTalk for TCP/IP. It has all of its benefits, nearly all of its features and it works with normal Routers and TCP/IP hardware.

OpenTalk is the perfect name.

And, FWIW, AppleTalk only has a bad name because the first version (Phase I) had a problem where it would get too chatty. This was fixed in Phase II which was released shortly after Phase II and has been available for over 10 years now. But people's opinion of AppleTalk was already ruined so it basically never recovered.

PS. A recent problem with AppleTalk is that the new Macs that could boot Mac OS 9 are way too fast for common routers. For instance, if the spanning tree protocol is turned on, it is possible for a mac to send a request about AppleTalk and finish booting before it got an answer. This was the origin of the message "Your AppleTalk network is now available" at bootup on a lot of macs.

Re:Bad Choice

[BurritoWarrior]

I can hear the IT folks gripping.

Yeah, well it's hard for us to find girls.

Slashdot has been taken over by Apple!

[Al Dimond]

I, for one, welcome our translucent overlords.

terrible name...

[rizzo420]

they should've named it iTalk to go along with all the other apple names.

Re:OpenTalk?

[McCall]

Maybe the FSF or someone in that league should try to trademark Open* names and reserve them for Open programs?

You idiot, Rendezvous is open

But then again, I don't expect somone with a UID as high as 761208 to know that...

Re:Apple Apple Apple ... Orange?

[Gannoc]

As for this article, let this be a lesson to you: if you sue Apple over a name, it is you who will end up having to change your name.

What? _Apple_ is changing their name, not the company.

I've heard of not reading the article (RTFA), but rarely seen someone who didn't even read the summary.

Confusing?

[pldms]

Given that the issue was that there were two things called 'rendezvous' the statement:

Rendezvous' new name will be OpenTalk

doesn't really help :-)

Re:Confusing?

[mcmonkey]

Given that the issue was that there were two things called 'rendezvous' the statement:
Rendezvous' new name will be OpenTalk
doesn't really help :-)

To avoid any future confusion, both products will be renamed. To OpenTalk.

All clear?

Re:In Other News...

[syates21]

Yeah that's the same.
TIBCO has had a patented networking protocol called Rendezvous for years that is the core of their whole business. It runs a few small systems you may have heard of like, oh, NASDAQ.

It's not too hard to see why they might be upset at another company coming out and promoting a completely different and unrelated networking protocol with the same name.

Re:Taco...

[ZackSchil]

I believe he was referring to the fact that the ZeroConf name was tossed out not once but twice, and the second time, it wasn't used even though the last name had to be discontinued due to legal issues. The name was crying, not the technology.

Can they rename to FireBirdFoxCaminoTalk?

[cant_get_a_good_nick]

Is there a Mozilla implementation?

To highlight the product similarities

[phoebe]

Tibco's Rendezvous can be used to the do same task as Apple's Rendezvous, i.e. dynamic configuration. They both use multicast and don't require server endpoint configurations like addresses, etc. However Tibco's Rendezvous can also do generic, certified, and transactional messaging and hence Apple's product description does harm by implying Tibco's software has less capabilities, i.e. inferior, to what it really is.

To update the trademark links, Tibco was formally Teknekron:

• Teknekron's trademark - filed July 10, 1995
• Tibco's trademark - filed May 20, 2002
• Apple's trademark - filed May 6, 2002

Re:Fianlly - a name that makes sense

[arkanes]

If you're an english speaker and you don't know the word "rendezvous" then you DESERVE to feel like in idiot. It's not a made up word, or even technical. It's in the dictionary. And not just the OED, it's in every 2 dollar cheapo Merriam-Webster dictionary that you got from a used bookstore in high school and you still keep around. What the hell is wrong with people?

Re:OpenTalk?

[argent]

it looks like Apple is trying to purposefully confuse people by prepending "Open" to this product

<sarcasm>Yes, deliberately using the term "open" to describe an open standard based on an open source project is just so sneaky and underhanded...</>

Re:Any OpenTalk/ZeroConf servers for *NIX?

[Twirlip of the Mists]

Yes indeedy. Apple has made the source code for a POSIX implementation of the Rendezvous daemon available on their web site so you can download it and build and run it on any POSIX-compliant system. (So they say. I haven't touched it myself in nearly a year.)

For something like a printer, your best bet would be a Rendezvous proxy service that runs on machine X and advertises a printer service on printer Y. It requires configuration on your part, but only once for each device or service you want to proxy. I believe the source for a POSIX proxy responder is included in the Apple source tree as well.