I'd be happy to look at this for you, but after working with FMP
since tango 2, I can't see that the single threading aspect of FMP is
causing resultsets to get mixed up.
On Mar 1, 2006, at 5:31 AM, Dave Lubovinsky wrote:
The problem is that the results returned as part of the query are
"partially" the incorrect results. The Witango query might be
calling for 10 fields, and the first few fields are the correct
results, while the subsequent 7 are actually part of another record
altogether. ie - A query of address information might return the
correct name and street address, but then grab the city/state/zip
from a completely seperate record. In the debug, I can actually see
it doing this, and I have been able to narrow it down to occurring
within proximity of other requests happening simultaneously, and
somehow in the threading of calls to the database, its mixing up
the results of the call.
[WiTango 5.0, FMP 5.5 Server, OSX 10.2, WebStar 5 & Apache servers]
Roland Dumas wrote:
the two things you did to make it better likely make it worse
default scope should be request and userref arguments should be
avoided
If your users are sitting behind a caching proxy server and
cookies are blocked, you're in the danger zone for this kind of
thing.
You'll need to make sure you have the nocache headers and also
append URL arguments that give random numbers to prevent the
caching of resultsets in your clients' proxy
On Feb 28, 2006, at 8:30 PM, Dave Lubovinsky wrote:
I am having the very same problem that Andrew describes here
(user scope VARS being shared amongst users by mistake...needless
to say, this is a serious issue). I approached it the same way as
Andrew did (using &<@USERREFERENCEARGUMENT> and also setting the
DEFAULTSCOPE in the witango.ini to user), but to no avail.
Does anyone know the answer to this problem? (Upgrading to 5.5 at
the moment is not an option.)
I have not encountered this problem in the past, but suddenly it
has showed its ugly face and is becoming a real nuisance. Can
anyone offer some advice on this???
Dave Lubovinsky
Carnegie Mellon University
Pittsburgh, PA
Andrew Derry wrote:
Hello,
We set up a few simple Tango apps a few years ago that I believe
were Tango
3.6 - Which were not all that long ago ported up to Witango
Server for OS X,
currently v5.0.1.065.
One app is a simple FileMaker DB search (If you can call
FileMaker a DB?) ;)
However since the upgrade, people have complained about getting
results
other than for what they searched... It turns out that if you
hit the page
from two different browsers at very close to the same time,
they'll both get
the results of one of the searches.
It's basically just a simple form where the user just selects
some values
out of the table to bring up the resulting matching records.
We just go:
<FORM METHOD=POST
ACTION="<@CGI><@APPFILE>?
function=search&start=1&<@USERREFERENCEARGUMENT>">
And then the TAF just branches on function and does a search on the
@POSTARG's
Actually, it didn't have that @USERREFERENCEARGUMENT at first, I
added that
out of desperation... But no luck...
I also thought to check the DEFAULTSCOPE in the witango.ini -
which for some
reason was set to request, which I couldn't even find in the
help (though my
help seems to not be easily searchable) - So I tried setting it
to user and
re-starting the witangod, but it didn't make any difference either.
Any ideas, anyone..? Do you need more info? It's been at least
a year or
two since I've had to do any Witango programming, and I never
did do
anything particularly complicated, so it might just be something
obvious to
others..
Any thoughts or suggestions would be very much appreciated.
Thanks
- Andrew Derry
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
