On 1/14/99 at 18:13, langfml [at] eng [dot] auburn [dot] edu (Matthew Langford) wrote: > In general, Perl and databases go together like (insert your favorite pair > here). Think serving up database pieces from a web site. Think of a > website which _is_ your database front end, across the world. > > Think of tying your database to sources of information on web pages across > the Internet, and updating the information continuously rather than at > painful intervals. > > Think of getting access to tools that already do these things for you, but > written for other databases. Through the magic of the DBI interface, you > could re-use them with little effort. > > Think of an easy tool to recognize and pull useful information from a > jumbled up text file, like the access log for a web server or the output > from some other program (an installer, say). > > And I don't even know much about MacPerl! Others could supply better > examples. > > What database wouldn't benefit from perl? Maybe your phone number file. I must not have expressed myself very clearly. I was not wondering why to use MacPerl- I think it rocks and am trying to learn as much as I can about it. What I was questioning was how much would be gained by using the glue module and AppleEvents rather than just communicating from/to MacPerl via AppleScript? As far as I know, all of the things that you mentioned are available either way and it's probably just a question of personal preference. BTW, FileMaker provides builtin web serving without the need to use a cgi of any kind and I don't think that it will work with DBI in any case. For relatively small, moderate traffic sites that do not require SSL, it is perfectly acceptable without bothering with a web server at all. Richard Gordon Gordon Consulting & Design Voice: 770-565-8267 Fax: 770-971-6887 ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch