[webteam] vendor lock-in, what the .... is it?

[Peter Saint-Andre]

Hal Rottenberg wrote:
> On 9/24/07, Peter Saint-Andre <stpeter at stpeter.im> wrote:
>> There *are* clients that are locked down to a specific service. IMHO
>> they are not of general interest (though they may be of interest to
>> users of that service), so perhaps it doesn't make sense to list them at
>> jabber.org anyway, because you could argue they are not jabber clients
>> in the first place!
> 
> Wait a second, think this through some more.  There are more than a
> few clients out there like this.  I can think of several examples off
> the top of my head, and most involve mobile or micro clients.  On
> those it can beneficial to move more processing to the server side.
> Also, I've seen companies do the multi-protocol services on the server
> side, kinda like Meebo.  In order to manage the integration of these
> services (or any other arbitrary reason an individual or company
> wants--it's a free planet), it can b ea perfectly valid scenario to
> tie everything to a vendor-managed server.

Right. But in that case, the service belongs under "IM service" instead
of "client" or "server".

I have nothing against dedicated IM services. But they're not clients or
servers as I would define those terms.

> And who says the software has to have a client-side piece at all?
> What about web clients?

A web client like ClarosChat or JWChat is a great thing. But that's
different from a web-based service such as Meebo.

/psa

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/webteam/attachments/20070924/b724ce2c/attachment.bin