Basic Server-side hosting requirements
Added by Anonymous almost 16 years ago
Legacy ID: #6262815 Legacy Poster: Joe Fleming (pongettikin)
Ok, sorry for the almost not about Saxon post but I have searched far and wide for a simple answer to this question and have been unable to find one. There are so many different web server configs that I have no idea what's what apart from Apache vs IIS and Windows vs Unix. So I can't figure out what basic setup I would actually need to get Saxon running on a web host in order to perform server-side transformations. The reason I ask is that I'd prefer not to splurge on anything like a dedicated or VPS host in the early going. My site may take off and expand or it may not expand past the core group of people that I know will use it now. I like XSLT but am finding XSLT 1.0 to be too much of a hassle with some more complicated ideas, such as grouping. I am willing to pay a little more to use XSLT 2.0 but by a little I mean paying a few dollars/month more for something like JSP support or a Tomcat host, not to pay $80 more for a dedicated host. So, what do I need to look for in a host? Will any host with JSP work? Will any host that can use servlets work? Will any host with Tomcat work? Will any host with .NET work? Do I need special access to register dlls or change environment paths which shared host would generally not allow? Is it easy to install a PHP bridge? (Keeping in mind that I don't necessarily know exactly what some of he above actually are) Or is there just no chance in the world that I'd ever get Saxon running on a shared server? Thank you for any help.
Replies (1)
RE: Basic Server-side hosting requirements - Added by Anonymous almost 16 years ago
Legacy ID: #6266654 Legacy Poster: Michael Kay (mhkay)
I don't feel very competent to advise on this, as I've avoid the issue in the past - Java hosting for a small enterprise does seem to be a messy area. First of course you have to decide whether to base it on Java or .NET. I would think that will depend primarily on which environment you are most comfortable with. I've looked into the Java situation a bit more closely than .NET myself. Generally, if you want cheap Java hosting, then I don't think you get high reliability, because you are sharing the environment with other users and if anyone crashes, the whole thing comes down. The cheap hosting solutions, for similar reasons, will constrain your ability to configure the environment, use lots of memory, and so on. The more you pay, the more control you get over your destiny.
Please register to reply