Ashvil wrote:

> First of all, I don't work for Jabber.com or will gain if they do well.

:) i didn't want to anybody think like this


> I do care that Jabber does well. For me, Jabber is a community that includes
> the Jabber open source server, other proprietary servers like JCS, Jabcast,
> etc., open source clients WinJab, etc., proprietary clients like Jabber IM,
> Vista, etc., clients libraries, server modules, innovative stuff like
> Jogger, etc. and finally the end users who use Jabber. From the technical
> side we are bound by the Jabber specification. So Jabber to me is MORE then
> just an Open Source project. I think this is the view in the Jabber
> community also, but if I am wrong, please correct me.

yes, you're right. This is jabber community. But to let it grow
we will have to let all the components grow or we will finish only
with free clients and some products that we can buy.


> With regard to my comment on JCS, my position is connecting to a Jabber
> server (whether open source or not) is better then connecting to an AOL
> server. Using a client supporting the Jabber protocol (whether open source
> or not) is better then using the AIM client. Both the actions GROW the
> jabber community, so if I want to use the open source versions of either the
> client or server, I can MAKE that choice. With the CLOSED AOL AIM protocol,
> that choice is not possible.

Of course but in a world where only people running small lans with
few dozens of users maximum use the open source server and all the
others have to buy commercial server.

no, but we can come into this conclusion in few months. 
As commercial server has almost everything - and oss has just the
basic functionalities. I've seen already some responses here saying
that - for this or for that you need to go and buy commercial server. 
And no discussion to change it in a way that people can download
free version with these features. 


> I never said in my email that we need to stop development of the server. I
> support your desire to for Jabber to be 'the best server'. All I said were
> two things with regards to the Jabber server, which I am expanding and
> repeating here

no, but we can come into this conclusion in few months.
As commercial server has almost everything - and oss has just the
basic functionalities. I've seen already some responses here saying
that - for this or for that you need to go and buy commercial server.
And no discussion to change it in a way that people can download
free version with this features.


> 1. If the Jabber server is used in a distributed fashion like sendmail and
> Apache, then that reduces the scalability requirement

yes, and i was thinking about this already. But the problem is that
people want's to have addresses like [EMAIL PROTECTED] not
[EMAIL PROTECTED] . Because this will be needed in the
future if your system will grow.

I found that we could use some kind of a gateway -
people connect to one server ( for example jabbber.org ) autheticate - 
get a token/session id - and then continue with a server 
l1.l4.dddljfds.jabbber.org that are real jabber servers.
The external traffic goes always trough the main gateway
jabbber.org and the internal traffic is going between machines
that knows that l1.l4.dddljfds.jabber.org and l2.l4.dddljfds.jabber.org
are in this same domain. The advantage is that
noone have to know about our internat structure, for the external
users we will always look like [EMAIL PROTECTED]

> 2. For ISPs that demand more scalability, let them use JCS, etc. now instead
> of choosing some closed solution like Odigo or co-branding AOL, Yahoo, etc.
> That way, when the jabber server meets their requirements, they can adopt it
> easily.

How somebody can adopt closed source software ?
Reverse engineer ?
Yes you are right but in my opionion if you choose
closed source software you go for closed solution.
As you don't have possibility to change tcp/ip stack
on M$ Windows you will not have possibility to modify
anything inside JCS.

---kuba troszok
[EMAIL PROTECTED]

_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to