in reply to Re: Re: Communication between seperate scripts
in thread Communication between seperate scripts

No-no, you are mistaken. Try it :)
  • Comment on Re: Re: Re: Communication between seperate scripts

Replies are listed 'Best First'.
Re: Re: Re: Re: Communication between seperate scripts
by jfroebe (Parson) on Apr 06, 2004 at 14:55 UTC
    You're both correct. In some early versions of IE (or 3rd party dialers), if you tried to access say http://localhost, it would attempt to dial if a network connection wasn't already available. I think it was in IE 5 or so where this was corrected. Note that this only affected the nntp, pop(2|3), smtp, http, https, gopher 'protocols'.

    No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

      Anyway, if you are writing a local socket application, then you would not have this problem, since it wouldn't have any IE dependancy. I tend to use local sockets and network oriented design techniques for IPC because they transition cleanly to networked applications when the need arises. Also they are very portable, as compared to something like memory mapped files, which are a Linux/Unix thing. Another option (maybe, depending on how you like the complexity, might be POE)

      One thing you have to watch for (not in this case I'm sure), though is whether a user running an application on the same machine (i.e. Linux remote users and/or Windows terminal server) can't play with the app. Local sockets bridge user boundaries, and hence can be dangerous if you don't build in the right protocols.

      Nice SG1 quote by the way, but IMHO nothing can beat Tealc's "Untamed equines couldn't drag me away..."