On Sunday 28 July 2002 23:49, Niall O Broin wrote:
> Yes, I know, dreadful subject. However, because of customer inistence we
> must deploy one project on W2K. This will thus be a WAMP project rather
> than a LAMP project. Of course as a highly skilled *ix person I can handle
> these Windows toys :-) but can anyone suggest any good educational
> resources for using Apache, PHP, Perl and MySQL together on W2K. Anyone had
> to do the same and found any particular nasty gotchas (yes, I know about
> the running Microsoft software one).
I had Apache, mod_php and MySQL running on windows 95 once :)
As far as I remember, the only problem was getting the MSI installer installed
on win 95, but that was mentioned in the docs. w2k has that built in, so you
won't have that problem. You should be able to find pre-built binaries for
win32.
For perl try activestate.com, that's worked for me in the past.
Nick
_______________________________________________
Webdev mailing list
Webdev@linux.ie
http://www.linux.ie/mailman/listinfo/webdev

No, hits=-8.2 required=7.0
	tests=KNOWN_MAILING_LIST,QUOTED_EMAIL_TEXT,REFERENCES,
	      SPAM_PHRASE_00_01,TO_LOCALPART_EQ_REAL,USER_AGENT_OE
	version=2.40-cvs

No, hits=-5.2 required=5.0
	tests=AWL,DATE_IN_PAST_06_12,KNOWN_MAILING_LIST,
	      T_NONSENSE_FROM_30_40,USER_AGENT_APPLEMAIL
	version=2.50-cvs

Why am I so passionate about decentralization? Because I believe some of
today’s most profound problems with networked applications are caused by
centralization.
Generically, a centralized political or economic system permits only one
answer to a question, while decentralization permits many separate
agents to hold different opinions of the same matter. In the specific
context of software, centralized variables can only contain one valid
value at a time. That limits us to only representing information A)
according to the beliefs of a single agency, and B) that changes more
slowly than it takes to propagate. Nevertheless, centralization is the
basis for today’s most popular architectural style for developing
network applications: client-server interaction using request-response
communication protocols.
I believe these are profound limitations, which we are already
encountering in practice. Spam, for example, is in the eye of the
beholder, yet our email protocols and tools do not acknowledge the
separate interests of senders and receivers. Slamming, for another,
unfairly advantages the bidder with the lowest-latency connection to a
centralized auction server. Sharing ad-hoc wireless networks is yet a
third example of decentralized resource allocation. Furthermore, as
abstract as centralization-induced failures might seem today, these
limits will _not_ improve as the cost of computing, storage, and
communication bandwidth continue to plummet. Instead, the speed of light
and human independence constitute _fundamental_ limits to centralized
information representation, and hence centralized software architecture.