Steve wrote:
I very much doubt that you set up your own mail server ( nope, you use gplhost
services instead )
Actually I have two of my own mail servers and I use GPLHost as well.
One day I will have 2 mail servers and no GPLHost... I'm just not that
confident yet :)
I think your point is right on the mark though!
If it wasn't for the RFC then my mail server, running postfix, couldn't
talk to your mail server (running what ever you run).
Skype doesn't have to talk to anything other than skype does it? Hence
it's an easier program to write, leaving more time to address other
issues like traversing firewalls (which is where we started this topic).
... So by your reasoning, email isn't finished either??
Correct. By my logic, nothing is finished because it's constantly evolving.
As for clients, is, for example, ekiga really that difficult to configure??
Personally I don't know.
Viks point, that I was following on from, was about the clients ability
to get though firewalls. SIP software isn't the only p2p type of
application that has this problem though it is?
Whatever, it's infinitely better than some closed product using 100% of the
available cpu on a PC running Microsoft windows... but doing what???
Now we're really heading OT... but I 100% agree with you that there's
stacks of software out there in the MS world that just has bugs in it.
To me, anything that causes 100% CPU is just a bug.
Cheers Don
