Slashdot Mirror
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.
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.
Okay, this time I mean it: No more product-based body modification.
Cue "Lindevous" jokes.
The Cheese Stands Alone.
Sounds too much like AppleTalk.
I can hear the IT folks gripping.
I, for one, welcome our translucent overlords.
I'm sure Apple registered that trademark a LONG time ago. In fact, I think it's been used before for something else.
LocalTalk, OpenTalk, PowerTalk, AppleTalk, MacinTalk, KanjiTalk, ZhongWenTalk, etc. etc.
they should've named it iTalk to go along with all the other apple names.
please me, have no regrets.
Now that Apple's got a pretty good speech-recognition and text-to-speech engine, all the networking talks have to compete with the real talking for cute marketing terminology, such as "PlainTalk."
[
Maybe the FSF or someone in that league should try to trademark Open* names and reserve them for Open programs?
You idiot, Rendezvous is openBut then again, I don't expect somone with a UID as high as 761208 to know that...
Maybe the FSF or someone in that league should try to trademark Open* names and reserve them for Open programs?
Under USPTO regulations, I do not believe that you are allowed to "reserve" trademark names. I believe that you can only trademark names that you are actually using in active commerce or that you are actively preparing to launch in commerce. This is probably a good thing, because otherwise it would be like the situation with domain names -- people registering hundreds or thousands of names that they have no intention of ever using on the hope that they will pre-empt somone else's usage, and then extort a payoff.
I think you misread/failed to read the article. Apple is changing their product's name. Tibco is not.
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.
Given that the issue was that there were two things called 'rendezvous' the statement:
:-)
Rendezvous' new name will be OpenTalk
doesn't really help
Slashdot looked deep within my soul and assigned
me a number based on the order in which I joined
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.
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.
Is there a Mozilla implementation?
Apple is one of the few companies creating innovative technologies and doing stuff that matters with it.
For example last night, I picked up an Airport Express. From unpacking to hearing streaming music on my stereo, less than 5 minutes.
Is WiFi new? No.
Is streaming music new? No.
But Apple has taken the same basic building blocks everyone else has to play with and made something innovative.
The iPod is the same story.
Frankly I'm surprised you can understand it either, with a UID as high as 212035!
What were you guys doing when Slashdot started taking accounts, reading Byte?
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:
Rendezvous/OpenTalk is an implementation of ZeroConf, ZeroConf is an open standard, therefore Rendezvous/OpenTalk is an implementation of an open standard.
Beyond that, Apple's source code for their mDNSResponder (the core of Rendezvous/OpenTalk) has been available under the APSL since it debuted in jaguar, and therefore is open source.
So I'd say OpenTalk is a reasonable name to use (espescially in comparison with AppleTalk which did the same thing in an apple only sort of way).
Shrewd marketing. Rendezvous always sounded kinda French to me.
Everybody knows us Amurricans in the red states don't like nothin' French. Suddenly I feel like goin' out and buyin' me a big bunch o' Apples!
When all you have is an axe, everything looks like a grindstone.
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?
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...</>
It does not get any better stealing from foreigners in this case the French.
How wouild you all feel if a French company decided to Trademark Meeting it's laughable.
Help fight continental drift.
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.
I write in my journal
To be honest, anybody who is genuinely in the market for TIBCO's Rendezvous is not going to confuse it with Apple's Rendezvous.
Think of Apple Rendezvous as a 4-door luxury sedan and TIBCO Rendezvous as a 150 ton mining truck. Yeah, they're both vehicles with four wheels, but you'd have to be an idiot to confuse the two, even if they share the same name. What's more, it's the mining truck company doing the suing--is it really plausible that customers for such a specialized product are going to confuse the heavy-duty industrial solution with the Joe Everyman one?
Obliteracy: Words with explosions