there are many reasons not to deploy on Windows, but none of these is
due to WebObjects.
I like to know what those are. My word is insufficiently convincing.
I fear, there is no point that will convince anyone in management.
But lets start with a few:
- Security - I think, you have more
Hello,
Does somebody have an Apache 2.4 module for Windows 32 and 64bits ?
Or a howto to compile it.
Le 18 mars 2013 à 22:13, Klaus Berkling kberkl...@dyned.com a écrit :
On Mar 18, 2013, at 12:54 PM, Markus Stoll wrote:
there are many reasons not to deploy on Windows, but none of these
there are many reasons not to deploy on Windows, but none of these is
due to WebObjects. WO is able to run on Windows just as fine as on any other
platform.
if you are bound to use IIS, you might consider this pull request
https://github.com/projectwonder/wonder/pull/386
which gives you an
On Mar 18, 2013, at 12:54 PM, Markus Stoll wrote:
there are many reasons not to deploy on Windows, but none of these is
due to WebObjects.
I like to know what those are. My word is insufficiently convincing.
if you are bound to use IIS, you might consider this pull request
On Mar 15, 2013, at 12:37 AM, Stéphan Mertz wrote:
We use http://wrapper.tanukisoftware.com, but look at the new WOStart from
the community. You can install it as a service.
WOStart, huh. You make my life easier, and very thankful for that. But I
needed a reason not to deploy on Windows.
Hi all.
I may have to deploy on Windows Server 2012 (2008 might also be a possibility).
If you deploy on 2012 or 2008, how do you run wotaskd as a service?
For 2003 there was Instsrv and srvany part of the resource kit. Is there any
equivalent for 2008/20012?
Thanks.
kib
The trouble with
