Neil Nelson wrote:

> Also Jure, I was just thinking that there might be a way to have

> the Apache web server send ICSA messages through to an ICSA

> routing server on the Linux box/ici_server.  That is, and it would

> require a bit of work and so we would not want to do this soon.

> Rob's icsa could communicate on port 80 as would be done by a

> web browser and connect to my Apache web server, which would

> then send the messages to an ICSA router that then sent the message

> to the proper computer.  This is rough, and it would be a bottle-

> neck but it is an idea. Something better might come out of it.



This is surely a way to go. You will want to put on some kind of

bandwidth limitator, so the thing doesn't bother other (direct

connection) users. The ICSA would just attempt to connect directly and

if it detects a firewall (messages don't go trough), it will notify the

user* and use the trough-server connection, while the direct one is not

available. I am thinking this will be a great advantage for users that

have firewalls and have nothing they can do about it at the moment they

need an ICSA service.



* = We can go for EWolf here if you want: Use notificators aka "EWolf:

Notify, Firewall, 10102" or write the status in a databank aka "Port

10102 = Firewall".



C'ya!



--

Cellphone: 0038640809676 (SMS enabled)



Don't feel bad about asking/telling me anything, I will always gladly

reply.

[AC/HFA(AS) -- no suprize]



Digging for info? Try AI Meta Search:

Http://WWW.AIMetaSearch.Com



MesonAI -- If nobody else wants to do it, why shouldn't we?(TM)

Http://WWW.MesonAI.Com

