In a message dated Fri, 25 Oct 2002, Sherm Pendley writes: > Unfortunately, the current version of CamelBones uses a set of > hand-rolled "wrapper" classes. So, in order to use "random" ObjC code, > you'll need to write a "wrapper" class around the relevant classes, like > so: > > @NSNetService::ISA = qw(Exporter NSObject); > @NSNetServiceBrowser::ISA = qw(Exporter NSObject); > > The next version - due in late Oct or early Nov - automatically > generates wrappers for all linked classes.
Well, I can certainly wait a couple weeks to do that part of it :-) > Rendezvous will only help with advertising and discovery of machines on > the network that provide a service. You'll still need to use traditional > methods to actually implement the service itself. Of course, if your app > uses a standard protocol such as HTTP or SOAP for low-level > communication, there are CPAN modules that will do much of the heavy > lifting for you. Oh, that's no problem, I've been writing networking apps in Perl for a decade. But dealing with UDP broadcast, discovery, etc., is not something I was looking forward to. Not so much in making it "work"--that's relatively easy--but making sure it's a good network citizen too and deals robustly with hosts coming onto and off of the network--that's hard. > > Ideally I'd like to have some sort of auto-discovery mechanism. > > If Rendezvous works as advertised, that's precisely what it does. I > haven't upgraded to Jaguar yet, and I'm very interested in hearing about > how well it works. I'll let you know. After I get the next version of CamelBones. :-) Trey
