Logical extension of MyWeb

Over a year ago, when the MyWeb service was given to me to make happen, I made a prediction.

At some point, they're going to ask me to provide pretty much direct file-system access by way of Apache.

It took over a year, and lots of instability probably contributed to it taking this long, but I just got the request to provide, "MyWeb, but for departmental shared areas. A sort of DeptWeb." That's right boys and girls, they want to provide departmental web-pages from Netware. While I'm cool with that in theory, the execution doth suck. And this is why.

You see, in order to provide that, I need to use mod_edir again. While I'm fully versed in it, mod_edir (and more specifically the LibC calls that allow it to work at all) isn't stable enough for production usage yet. NW65SP3 might fix that, but I'm still a few weeks away from knowing that for certain. If SP3 does fix it, then yes, we can do it. If it doesn't, then DeptWeb will have the same uptime as MyWeb. Which, if you hadn't noticed, is best described as, "most of the time, we think."

No, MyWeb is not a service capable of 'two nines' uptime. Heck, Intermapper reports our uptime for student MyWeb at 95.7%. Hardly a reliable service. DeptWeb will be just as wibbly, and I'm pretty sure that won't sit well with the grand high muckity mucks who send out an all-campus mailing for some prestige event, and the URL to the PDF that explains it all is not working.