[revServer] process timeout issue
mikekann at yahoo.com
Wed Aug 4 13:04:47 CDT 2010
One weird aspect to the situation is that the on-rev server is physically in Texas (Houston) and the two people reporting problems (Jerry and Jeff) are also in Texas (Austin).
--- On Wed, 8/4/10, J. Landman Gay <jacque at hyperactivesw.com> wrote:
From: J. Landman Gay <jacque at hyperactivesw.com>
Subject: Re: [revServer] process timeout issue
To: "How to use Revolution" <use-revolution at lists.runrev.com>
Date: Wednesday, August 4, 2010, 12:51 PM
On 8/4/10 3:49 AM, Chipp Walters wrote:
> I imagine anyone Googling for information on RevServer would certainly find
> those. They do damage-- and deserve a rebuttal. But, of course, without a
> recipe or any sort of proof, a rebuttal is pretty much impossible. That is
> why I've called on Jerry to try and work with RR to create a recipe so that
> a fix can be found.
This does bother me, especially since several of our web gurus on this list can't reproduce the problem. I of course believe there's an issue somewhere because I'm sure Jerry and others wouldn't just make this up, but it appears to be obscure. It seems unfair to post damaging accusations without giving the RR team enough info to respond and fix it.
> Frankly, I was pretty much taken by surprise when Jerry posted his issue
> with RevServer so publicly, especially when Kevin has most generously
> allowed Jerry and company to harvest customers directly from this list--
> something I have never seen another company do.
RR has worked very closely with D&M in the past to resolve issues in all their other products. They offered to do the same in this case too but got no response. That makes me wonder if the stated reason for the move to PHP isn't a red herring and there are other unspoken reasons for the reversal.
-- Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
use-revolution mailing list
use-revolution at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode