Hey Lars, 2009/7/8 Lars Hamren <[email protected]>: > Hi, Koen > >> I looked at your previous version and liked it alot. > > Thank you, that's nice to hear. And I like Wt a lot. > >> I am still thinking about how to assume a sensible default... > > In yet another version, now uploaded, I have implemented the > following: > > If the user specified a server type, use it; > otherwise, first try "", then "http".
I feel it is becoming a bit too complicated, which could easily lead to frustration for novices... The hard problem is how to differentiate between FastCGI (where no parameters can be passed) and HTTP (which should be "easy" to run). Perhaps this is the correct solution: if a parameter (-s) is passed, use that one; else read the value set in the config file (config file from -c argument or standard location), use that one; else if only single connector is configured; use that one; else fail. In this way, for FastCGI you need to put it in the wt_config.xml; For the built-in httpd, you can put it in the wt_config.xml or pass it using "-s http"; The only tricky problem is a circular dependency between the "-c config.xml" parameter, and the <connector>http</connector>, which may be handled by always checking for the '-s' and '-c' command-line arguments (and not only in case of the wthttpd) ? Regards, koen ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
