>At 23.39 +0100 1999.11.14, Axel Rose wrote: > >I try to write a CGI. I need AppleEvents. I tested Mac::Glue. > >This works but is too slow for my target application. > >I still think that you are better off writing your own "server" in Perl on >some alternate port so you don't need to worry about startup times. Why is >this solution insufficient? If I setup my own http server process in MacPerl I have to a) connect my main service (http on port 80, accessible from everywhere, WebStar with realms, etc.) with the MacPerl service on a different port on the same machine b) have all request serviced by the MacPerl process a) I simply don't know how, especially how to handle the different port when accessing the whole system from outside through a firewall b) is insufficent > >IMHO only a dozen or so people are able to work efficently > >with MacPerl/CGI and AppleEvents driven databases. > >Well, I don't think anyone is able to work efficiently with MacPerl CGIs, >of any kind. MacPerl CGIs just aren't very good for anything serious. It's sad to hear that from you. My hope though is that the next MacPerl release makes CGIs easier to use (threads). Many regards Axel ---------------------------------------------------------------------- Axel Rose, Springer & Jacoby Digital GmbH & Co. KG, mailto:rose@sj.com pub PGP key 1024/A21CB825 E0E4 BC69 E001 96E9 2EFD 86CA 9CA1 AAC5 "... denn alles, was entsteht, ist wert, daß es zugrunde geht ..." # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org