WISP sounds really interesting - however, I cannot seem to get it
working "as advertised"
Using the Witango 5.5 server on Mac OS X, Apache 1.3+, Java 1.4.2
clients.ini file edited as follows
*****
[Witango Client Definitions]
mod_witango55_apache1.so=
wisp=
[mod_witango55_apache1.so]
ERROR_HTML=/Applications/WitangoServer/5.5/MiscFiles/clienterror.html
REGISTER_EXTNS=tcf;taf;thtml;tml;wws
REPORTCLIENTERROR=TRUE
SENDFULLHEADER=false
WITANGO_SERVER=127.0.0.1,18155
[wisp]
WITANGO_SERVER=127.0.0.1, 18100
ERROR_HTML=
REPORTCLIENTERROR=TRUE
DOCUMENTPATH=/Library/WebServer/Documents
****
Edited wisp.ini as follows
*****
[Witango Client Definitions]
WispClientDemo=
[WispClientDemo]
WITANGO_CONFIGPATH=/Applications/WitangoServer/5.5/configuration
*****
Put wisp.ini and WitangoClientDemo.jar in the same directory
/Library/WebServer/Documents/nidb
In the same directory, have a taf (dts.taf) that just returns seconds
for timestamp
(restarted WITANGO server)
In terminal,
cd to directory where these files were all located
then ran
java -jar WitangoClientDemo.jar dts.taf
2
<HTML><H3>Client Error</H3><P>Can't connect to the application
server.</P></HTML>
So what am I doing wrong? Why can't a connection be made? I cannot
find any support info at the Witango web site to assist, other than
the html page with the WISP demo file, which I attempted to follow
exactly as described.
On Mar 16, 2006, at 7:45 PM, Customer Support wrote:
http://www.witango.com/downloads/WISP.zip
Regards
Witango Support
On 17/03/2006, at 7:04 AM, Dave Machin wrote:
Where can we find more information on WISP?
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, March 16, 2006 10:05 AM
Subject: RE: Witango-Talk: Timeout after 6 minutes
Hey there,
This is a perfect example of what WISP does really well. I have done
extensive testing of huge time consuming loops (millions all
querying)
using WISP and this is by FAR faster, more robust and more stable
than
using a web interface and relying on the browser, internet
connection, iis
(or other web server), and witango client to interface with the
witango
server. This resolves the need to do a constant postback and cuts
the time
to iterate through a big jobs to less than 10%.
Also consider the user experience, it's not so good sitting
around for 6
minutes wondering if the process works.
I would recommend setting up an app that executes a call to the wisp
interface, let the interface do the work and report when it is
done. Then
your user is doing what matters.
Even better, set up the process to run on a timed basis and
schedule it.
There are so many better ways than to use the web client.
Peter
____________________________________________________________________
____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
