I'd prefer either using PWLib PServiceProcess feature and don't introduce any ifdefs or split gk.cxx into two or more parts, so we have a common code, windows code and unix code. ----- Original Message ----- From: "Franz J Ehrengruber (iptelenet)" <franz@xxxxxxxxxxxxx> Sent: Tuesday, July 20, 2004 4:19 PM > > Howabout stating as a service when one of the 5 arguments you mention > > are on the command line ? Or a switch -RunAsService ? > I like that one too. Disadvantage - if users run the gk as a console process > only the executable contains the redundant service code which may be > significant. > > > Is there a way to avoid the #ifdef ? I don't like having to provide 2 > > different executables. > Advantage - easy segregation of service versus console app code. > > The 3rd option is perhaps not so popular, but MS ceases Windows 9x support > in the near future. From that point of view we could perhaps scrap the > console app all together and concentrate on a sole service process > implementation.(Windows only) > > Franz. > > Michal, your comments please - thank you. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
