FWIW.
I just rebuild DynEd's web site. Certain components are static HTML others are not. These are basic solutions nothing earth shattering (DynEd has other apps that are, IMHO).
Support: Site Search: Documentation: Videos: Customers requesting information: Getting support:
(I use some AJAX but I don't hide WebObjects in the URL, the servers is an Xserve running 10.6.8, Wonder monitor and wonder wotaskd)
We also use Wonder when people register their installation codes (through our Mac/Windows client application) which was based on FileMaker Pro and a FileMaker Pro plugin, now an apache module and Wonder.
For the web site and our bigger projects, WebObjects, even non-Wonder, hasn't failed us. And doing what we're planning we do in WebObjects/Wonder because we don't have to worry about it, we can just focus what we need done.
We have payed for fixes in Wonder before via consulting services (thanks Chuck) if we can't fix it/contribute ourselves. This seems to be a good way.
kib
"We keep moving forward, opening new doors, and doing new things, because we're curious and curiosity keeps leading us down new paths." Walt Disney
Klaus Berkling Web Application Dev. & Systems Analyst DynEd International, Inc. www.dyned.com
|