Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!haven!mimsy!tank!gargoyle!dawyd From: dawyd@gargoyle.uchicago.edu (David Walton) Newsgroups: comp.sys.mac Subject: Re: What I'd like to see in the AppleShare of the 90's Summary: Broadcast just ain't enough. Keywords: accounting, communications Message-ID: <583@gargoyle.uchicago.edu> Date: 17 Jan 90 01:08:41 GMT References: <25184@brunix.UUCP> <25862@cup.portal.com> <25447@brunix.UUCP> <25942@cup.portal.com> <1990Jan15.173834.27744@phri.nyu.edu> <581@gargoyle.uchicago.edu> <19068@netnews.upenn.edu> Reply-To: dawyd@gargoyle.uchicago.edu.UUCP (David Walton) Organization: U. Chicago Computing Organizations, Academic and Public Comp. Lines: 29 In a previous article, I complained about AppleShare's lack of tools for either accounting (tracking users' activities) and communicating with said users over the network. Several folks recommended Broadcast. While I like Broadcast and use it on my machine, it doesn't address the basic question, which is: How do you communicate with clients (users) when they are either anonymous (logged in as guest) or off in buildings which are miles away? It's a pain to make sure everybody has broadcast installed if you've got users spread all over the place, and it's impossible if those users are anonymous. Moreover, if some of your users are logged in anonymously, by definition it's impossible to tell who they are so that you may send them messages. In short, while Broadcast is a partial solution (at least to one of my complaints), it doesn't address what I see as the root of the problem: AppleShare itself doesn't provide such tools, and it should. I just don't see that adding these functions to AppleShare would be that difficult. (And we are after all saying what we think the future AppleShare should have...) -- David Walton Internet: dwal@tank.UChicago.EDU University of Chicago { Any opinions herein are my own, not } Computing Organizations { those of my employers (or anybody else). }