Rendezvous Session Notes While I realize I will have to cut out early, here are my initial impressions from the Rendezvous Session:
They've moved their presentation from PowerPoint to Keynote for this presentation, having migrated it over for this session. Keynote's great in practical value.
Scott Sheppard and Adrian Mayo from OSX FAQ are running the presentation.
What is Rendezvous from the User's Perspective?
Three Macs, two printers and an Airport. Now what?
Automatically form a network, no manual config
iChat is configured for Rendezvous network use. Will discover all local iChat services that are running on a local net.
Rendezvous in Printers:
Printer manufacturers are incorporating Rendezvous. ALl Macs connect will see the service, as its advertized, either in color or B&W. Being adopted by Epson, HP, Lexmark, Canon, Xerox, etc.
Mobile phones will work w/ Rendezvous to access a network and sync.
Consumer devices like TiVo and Stereos will work with iTunes eventually.
Sybase and WorldBook have both adopted stuff to work with their suite.
You can surf via http://another-computer.local if that other computer has rendezvous enabled file-sharing or web-sharing turned on.
On to the "geeky" stuff...
ZeroConf runs on top of the existing TCP/IP stack in order to be chatty like AppleTalk was in OS 9. We see ZC for the first time in 10.2 Jag.
What is ZC networking?
A tech to enable plug and play networking. Doesn't require special servers, or manual config. It's cross platform. Things automatically locate each other and automatically share files and printers, nothing you need to do to set things up to talk to each other.
But the problem is that it's a work in progress. Apple's leading the pack, but others are joining along, including Philips and TiVo and others. Not yet been employed yet to build nets as much as they'd hope.
But what's the scope? Not aimed at really large network structures. It's all aimed for within a subnet currently. Really aimed for an impromptu network. Like a LAN party.
<insert boring ass over-simplified history of TCP/IP here>
this can be simplified by saying the Mac used to run two protocols: TCP/IP and AppleTalk. This is bad, twice as much can break. So, Apple dropped AppleTalk. Why? Well, some apps had to handle two protocols, which sucked. So OS X moved us to Unix, which meant TCP/IP is the native tongue, AppleTalk is worthless. TCP/IP is built for massively large networks, but not without some attention to details. But we want things to be easy when it comes to little Impromptu networks.
The Goals of ZeroConf.
To enable Zerconf and casual networks
Run over TCP/IP
Run alongside configured Networks
Must be secure
Must not break existing applications
The services of ZeroConf
Address allocation - unique
Host name allocation - unique
Host name to IP address resolution
Service discovery
Multicast
This is where I had to go...more later when I find the PowerPoint on their website.
5:10:22 PM
|