If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register or Login
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Re: IP Based SEVERLESS Chat..

Thats odd cause i was just thinking about trying to implement something like that in PHP, the person uploads the file then when the other user logs onto the website he will be able to download it. Bit like email i supose, but since its slow ill keep looking into the person to person thing. Whats a chaching Proxy server?

Re: IP Based SEVERLESS Chat..

After a long time of on the shelf i've started to further the usability of this application.

Bug Fixes:

Well None, everything has been very stable and no one has reported anything..

Additions:

Remote Sub-Net searching: I've added quite a lot of code to enable two users on seperate subnets to connect. one user needs to enter a ip address or even the subnet address (ie 196.23.0.0) and the proggy will connect, Users on both subnets will now be able to communicate with each other.

Note: As i do not have access to a multi subnet network, I have as yet been unable to fully test the functionability, but prelim tests show that this feature works as expected.. Any and all feedback on this will be greatlly apreciated..

Re: IP Based SEVERLESS Chat..

I can't seem to recreate the problem, who knows what I managed to do last time. Well at least it all works fine now. Just a small note for the login screen, is there meant to be a space at the preceding of the port number?

I've been looking at sending messages over the internet and it seems you need a dedicated server application on a computer that can accept requests from outside systems. Unless all the users are prepared to adjust there LAN IP filtering.

Re: IP Based SEVERLESS Chat..

The space in the port number is a by product of Str([number]), and is actually the place holder for the sign. It has no effect on the application..

The problem here is the ip filtering, most systems will allow a outgoing port request, and let back in the reply, but will block any incomming requests.. This is one of the problems faced with this application...

This is meant to be serverless, so i dont want to write a seperate Server application. I'm trying to change the face of over the net chat applications. No server = No way to stop the chat..

Take MSN for instance.. put the MSN server offline and milions of ppl cannot chat.. but if you go serverless there is no way to stop the chat...

Think about it... Almost everything we work on runs on some or other server.. Land Line Telephones (An exchange), Cell phones (an exchange), Internet (ISP's).

And now look at travel... if you want to visit a friend that stays a few blocks away, you dont travel to the center of town, stop off at a "Library" and look up his address, then travel back along most of the same road to his house..

I feel that internet chat shoud go the same way... If you know the address, why must you allways pass through a server(the Library) to chat to your mate..

Lets look at our analogy again: what happens if the "Library" is closed for some reason, now you cannot visit your mate, even if he is at home. But in reality you know where he stays because you were there before, so you go to his place directly, chat app's need to go the same way: Well atleast thats the way i feel...