How to use socket commands and function in a .irev script
Jérôme Rosat
jrosat at mac.com
Sun Sep 20 14:32:42 EDT 2009
Le 20 sept. 2009 à 15:55, Jim Ault a écrit :
>
> Programs and scripts running on a web server are running under
> Apache, which has environment variables set when it loads. I don't
> know of a way that a process running in Apache can open and close
> sockets between processes. Opening and using sockets to the network
> is done all the time.
>
> Jim Bufalini correctly mentions the POST command as a way of using
> port 80, a default for Apache.
> I think you would have to modify the httpd.conf file and tell Apache
> to listen on those ports.
> One catch to this is that any program or script that is opened in
> Apache would be working with that port.
I am not certain that it is possible to modify this file in an one-rev
account.
>
> One serious difficulty with this is that Apache will launch a
> script, run it, then clear that memory. The next request starts a
> new instance of the script. This is how multiple users can access
> the same 'web page' and see it as their own session. The process in
> Apache dies after the page is sent to the browser, thus there is no
> running program in Apache to receive the packets sent.
I believed naively that a script .irev behaved like a stack and
"persist" in memory. I conclude that a .irev with an on-rev web
account does nothing more than a "ordinary" hosting account with
Revolution CGIs.
>
> Basically, everything on a web server is accessed by telling Apache
> what you want and how you want it.
>
> I would like to learn more about On-Rev surprising features and
> limitations so feel free to jump in if my comments are not telling
> the whole story.
>
> Jim Ault
> Las Vegas
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
More information about the use-livecode
mailing list