1 |
Am Tue, 18 Dec 2012 14:50:51 +0200 |
2 |
schrieb Alan McKinnon <alan.mckinnon@×××××.com>: |
3 |
|
4 |
> On Tue, 18 Dec 2012 12:30:16 +0100 |
5 |
> Marc Joliet <marcec@×××.de> wrote: |
6 |
> |
7 |
> > Am Mon, 17 Dec 2012 18:04:46 -0800 |
8 |
> > schrieb Grant <emailgrant@×××××.com>: |
9 |
> > |
10 |
> > [...] |
11 |
> > > > XMPP clients are a dime a dozen, take you pick: pidgin, kopete, |
12 |
> > > > telepathy and a hots of others. |
13 |
> > > > |
14 |
> > > > Servers are another story. All of them that you can lay your |
15 |
> > > > hands on seem to suck big eggs big time. ejabberd is the only one |
16 |
> > > > I found stable enough to actually stay up for sane amounts of |
17 |
> > > > time, and not DEPEND on java. |
18 |
> > > > |
19 |
> > > > But that info might be well out of date, I haven't looked at our |
20 |
> > > > jabber server for ages. There's no need to - the techies all |
21 |
> > > > gravitated by themselves over to GTalk and Skype, claiming that |
22 |
> > > > the cloud services did everything they needed and more, and it |
23 |
> > > > was there, and it worked. Our in-house jabber server - not so |
24 |
> > > > much. |
25 |
> > > > |
26 |
> > > > Can't say I blame them. It's true. |
27 |
> > > |
28 |
> > > Thanks Alan, this is just the kind of info I need. It sounds like |
29 |
> > > I would be better off with a cloud solution for collaborative chat. |
30 |
> > |
31 |
> > Just out of curiosity: why couldn't you use a Jabber client with |
32 |
> > Bonjour/Zeroconf support (all or most of them?) within the company |
33 |
> > (which is what this is for IIUC)? With Zeroconf, the Jabber clients |
34 |
> > "find each other", then you wouldn't need to bother with setting up a |
35 |
> > server. |
36 |
> > |
37 |
> > Or is Zeroconf problematic? I know Pidgin can do Zeroconf on Windows, |
38 |
> > even if you need to manually install a separate package for it to |
39 |
> > work. |
40 |
> > |
41 |
> |
42 |
> That doesn't really work when one fellow is at his desk in the office, |
43 |
> another at home on an ADSL connection and the third is a 3rd party dev |
44 |
> based in Los Angeles. That's quite common for me. |
45 |
> |
46 |
> Zeroconf has it's uses, but it does have a rather narrow scope as to |
47 |
> where it can work. |
48 |
|
49 |
I understand that, I just thought that Grant was talking about a purely |
50 |
internal chat solution (like my workplace has) - he did say "within a |
51 |
company" (though admittedly in retrospect I realize that that doesn't |
52 |
necessarily mean *physically* within the company). |
53 |
|
54 |
Regardless, it isn't clear to me that Grant is talking about something that has |
55 |
to be available from anywhere. While he is apparently gravitating towards a |
56 |
"cloud solution" for chat, my understanding is that that is because then he |
57 |
doesn't have to manage his own server. All of the other solutions mentioned |
58 |
could be for internal *and* external use. |
59 |
|
60 |
Anyway, I was just curious and thought that if this is purely for internal use |
61 |
than Zeroconf might be a good server-less option for chat. |
62 |
|
63 |
-- |
64 |
Marc Joliet |
65 |
-- |
66 |
"People who think they know everything really annoy those of us who know we |
67 |
don't" - Bjarne Stroustrup |