Joel wrote: >>The question is: Is that a standard courtesy, or should I tell people to >>find out about the path? > >Standard courtesy, for some OSses, not necessarily followed. Some >providers even use systems that require a second password -- one to get >on the system, and one to access the area requested. A note of >explanation about the path would not be out of order, ergo, that it >refers to a directory or other sort of user area, and that some systems Ok, I'll do that. Examples of typical paths are appreciated (you may not want to bother the list with that). >Do you plan to deal with proxy issues like socks servers? I, for one, >would sure like someone to find some magic way through NT proxy servers. No! I'm just trying to provide Macintosh users with introductory information to a particular topic. Made together with Vittorio Barabino there is an Applescript tutorial (MacScripter's Magazine) at http://macscripter.net/magazine.html. I've about finished a 2 part introduction to Perl (drafts available on my home page at www.knoware.nl/users/bsfa/index.htm. Until it is finished it is NOT to be distributed. Rich Morin promised to carry it when they are finished). And now I'm working on a CGI introduction. I think that if Macintosh users go one step further in providing each other with information, the Mac is the platform to beat. If you check out MacScripter's Magazine, you may agree that an interactive multimedia project beats text based approaches hands down. We've had very favourable reactions to it. I certainly hope that more people follow what Vittorio and I started, and that soon I can find an interactive tutorial on a topic that interests me. For MacScripter's Mag, other people stepped in and have provided translations, so we are reaching more and more people. The advantage of multimedia projects is that Mac magazines can carry them. I know of at least two magazines that did . Making a tutorial isn't difficult (I've a template on my web site for those who would like to give it a try, and the program used to make it is free). A tutorial consists of screenshots and a little text (less is more. But you have to think over each sentence a bit longer). As to why I will not write a tutorial on NT proxy servers: I would like to write about things I'm an expert on but there aren't (except patents, perhaps). So I write about things that interest me, but which I have to learn on the way. The positive thing about that is that I recognize which problems other people will face. I hope to present you with a draft of the CGI tutorial soon. Bye for now, Bert ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org