Archive of UserLand's first discussion group, started October 5, 1998.

Re: Firewalls, Hooray

Author:David Valentine
Posted:5/5/2000; 5:22:49 PM
Topic:scriptingNews outline for 5/5/2000
Msg #:17041 (In response to 17035)
Prev/Next:17040 / 17042

Dave, what part is wrong?

I think he got this part correct: Pike needs to be able to connect from client to server, and keep and open connection.

The server to pike connection is broken out of the gate (personally): 1) It does not work with a NAT. You can only dedicate on computer to pike (or one computer per incoming port) 2) Sending the http request for pike over port 80, fails with my ISP's web cache. 3) Firewalls don't like incoming connections.

The only problem with Pike(more it is an XML-RPC problem) is that it uses a Web server as a communication method. I think what he means is that xmlrpc should be running over it's own port, and not port 80. It uses the http standard as it's communication standard. It can run over port 80, but it's best that it has it's own little region.

One of the reasons for having it's own port is so that it does not get f&*#(d with by port 80 web caches. Another is that a port can be opened in the firewall for it.

There are responses to this message:

This page was archived on 6/13/2001; 4:55:06 PM.

© Copyright 1998-2001 UserLand Software, Inc.