On Feb 7, 2004, at 10:49 PM, Jared McIntyre wrote:
> Actually, now that I think about it, All probably wouldn't need to be
> a group. A function like [[ServerDataManager sharedInstance]
> getEnumeratorForGroup: groupID] would return an enumerator that would
> walk through all servers in that class.
I guess my question is, who generates the contents of a group? A
"smart group" has contents that will need to be dynamically regenerated
as servers come and go via Rendezvous or as the user adds/removes
static servers. This could go in your class, or it could go in some
GroupManager class that uses the enumerator returned by your class as
its starting point.
> Actually, I don't know if you were thinking of smart lists when you
> mentioned listing everything that matches "*.mybigcompany.com," but
> that has interesting potential and shouldn't be too difficult to
> implement in this scheme, though I'm guessing it won't be implemented
> in the initial release.
Yep, this is exactly what I was thinking of. We don't need to
implement this for the first go-around, obviously, but I think we
should design with it in mind as it's relatively easy to add, and very
nice for end-users.