In a message dated 12/30/04 10:40:03 AM, [EMAIL PROTECTED] writes:
> I think Dar's got the best way.� Have the Rev stack accept connections on > some obscure port; then the browser can make http calls to it on that port. > If it's all running on the same machine, use the address 'localhost' or > '127.0.0.1'.� If you want to stay on the same page, you can use an iframe; > javascript (or even a simple link with a 'target' attribute) can change the > src of the iframe to the results of a call to Revolution.� Either you could > just use this to display the result to the user, or javascript could read > back the text from the iframe in order to further process it. > ok - - - I'm going to give that a try. I know how to get Rev to listen to ports, but I'm a little rusty on the 127.0.0.1 technique on the javascript side. So if I have Rev listening to 127.0.0.1 port 1986, and I don't want the ahref to go to a new page, is the only way to accomplish this to create an invisible iFrame with a different target name? <a href="127.0.0.1:1986" target="invisibleframe">Click me to talk to Rev</a> That type of thing? _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
