🚀 go-pugleaf

I'm currently working on a project where I need to munge about in
NetInfo to store network-wide defaults and the like.  I finally
think I've got enough of an understanding so that I'm not entirely
lost, but the netinfo stuff (and the NIKit) is a wealth of
undocumentation.  Netinfo is very, very flexible, but alot of
programs simply don't take advantage of it - and after spending
the past week banging at the access routines, I can understand why!

Oh, what's my Q?  Well, does anyone out there have any documentation
on the Netinfo stuff?  Or the NIKit stuff?  I guess I'm looking
for stuff more in the line of tutorial information, though I will
take anything I can get.  Example code is wonderful, _especially_
if it accomplishes modification to the database.

It's not so much that I'm unable to get anything done - I've almost
finished the first stage of the project, and it actually seems to
work.  What I'm looking for, though, are tips and tricks.  What
stuff I shouldn't muck with.  The best way to go about installing
a new set of properties for a directory.  What do the routines
return when there's an error (I know, ni_status, but I'm looking
for something more in line with the ERRORS section most of the 2nd
section of Unix Manual pages includes)?  Does it make more sense
to go insane caching information, or is reply time reasonable?
When do the differences between clone and master servers make a
difference?

I'm interested in any info out there.  Thus far, I see no reason
not to collect any information, bang it around, and pop it onto
the archives.  Netinfo isn't exactly something you want any old
idiot to be messing with, but I'd be interested in making it so
that a sufficiently intelligent idiot can :-).

[After the past week and more of working with Netinfo, I can tell
why the NeXT Netinfo utilities have so many limitations, like to
two-level domain hierarchies.  I wonder if there are only three
people at NeXT who understand the code to the point where they can
write the utilities, and those three people are so in demand that
they just don't have the time to get rid of the limitations :-).]

Later,
--
scott hess <scott@gac.edu>   <A GUI is to a command-line as a TV is to a book>
12901 Upton Avenue South, #326  Burnsville, MN  55337  (612) 895-1208 Anytime!