Sun Launches Instant Messaging Server 172
theIG writes "According to this article at geek.com, and another one at InternetWeek, Sun has shipped the first part of its new enterprise collaboration platform to compete with Exchange and Domino. Dubbed 'Sun ONE Instant Messaging 6.0,' this server will work with other products to be released in May, to allow a single login for all of its services that allow connections from outside a corporate firewall." Instant messaging is becoming increasingly popular in the workplace. Local messaging servers like this were only the next logical step for businesses which don't wish to rely on an outside network for their messaging.
What's Wrong with Jabber? (Score:5, Interesting)
Re:What's Wrong with Jabber? (Score:5, Informative)
It's like wanting jabber to integrate with yahoo mail and yahoo calendar, along with the privacy.
Not to slam jabber at all, just the right tool for the right job, eh? Just one that requirs sun software
Re:What's Wrong with Jabber? (Score:4, Insightful)
Re:What's Wrong with Jabber? (Score:3, Insightful)
Not that its proof of anything but Oracle has gone down this path [slashdot.org] as well on the integrated IM services.
Re:What's Wrong with Jabber? (Score:3, Insightful)
Re:What's Wrong with Jabber? (Score:2)
Re:What's Wrong with Jabber? (Score:2)
Jabber for as much as I love it does not seem to be making the headway thats needed to make it a leader in the field. Pehaps if the Linux distis started bundling preconfigured jabber servers that can be easily made to interoperate/connect it could happen but at the moment it just doesn't have the expose and userbase it needs to go big time.
.
Re:What's Wrong with Jabber? (Score:1)
If you want a quick jabber server setup you should look at JabberD Quickstart [jabberstudio.org]
From the page:
The JabberD Quickstart package provides a graphical, user-friendly way to install, configure, and manage the JabberD instant messaging server. No hand-editing of XML files, no need to create spool directories, no messy configuration changes -- just a simple, step-by-step setup script that does all the work for you. It's the easy way to get started with Jabber.
Re:What's Wrong with Jabber? (Score:1)
Re:What's Wrong with Jabber? (Score:3, Informative)
Re:What's Wrong with Jabber? (Score:1)
Re:What's Wrong with Jabber? (Score:5, Insightful)
It's like wanting jabber to integrate with yahoo mail and yahoo calendar, along with the privacy.
Not to slam jabber at all, just the right tool for the right job, eh? Just one that requirs sun software
Why not? Jabber is *not* an instant messaging protocol. It just happens to be useful for instant messaging
Jabber is a protocol for streaming XML. In this paradigm, why NOT use it as a transport for all sorts of other services, such as calendar information, etc.?
Ok, now for the privacy portion-- authentication and encrtyption are both supported by many Jabber clients and it would not be hard to impliment an X509-based encryption structure along with a directory service (AD, NDS, OpenLDAP, etc).
The problem is not with Jabber. It is with the fact that there are no open-source enterprise groupware servers to compete with Exchange. I really wish Sun would take the lead with open standards, but they have not because I am sure they want to create lockin.
Re:What's Wrong with Jabber? (Score:3, Interesting)
That's like blaming MS for not using Linux's drivers. They don't work together.
Re:What's Wrong with Jabber? (Score:3, Interesting)
What Jabber are you referring to? the core protocol or the many proprietary or opensource implimentations?
It doesn't integrate with sun's suite.
Sorry, but that is like saying that TCP doesn't integrate with Windows 98. In reality, it would be a bit different-- one would have a program that would *use* TCP and integrate with Windows 98, but TCP by itself does not integrate with anything other
Re:What's Wrong with Jabber? (Score:3, Insightful)
Either. Sun see's it more fit to use a certain protocol as well as software to work with their suite. They may do a better job than Jabber, i can't say.
Point is, they don't want to use jabber, that's fine. The protocol they develop becomes their thing. WHo cares if you have to use it? If
Re:What's Wrong with Jabber? (Score:2)
It has occured to me that we really don't know that Sun is *not* using this as a core protocol...
My point was more of a Ja
Re:What's Wrong with Jabber? (Score:1)
Jabber doesn't need to explicitly support calenders and email notification any more than the IP standard needs to have a se
Re:What's Wrong with Jabber? (Score:2)
Re:What's Wrong with Jabber? (Score:2)
It was just a design decision, not a religious decision to not use Jabber's protocol IMHO.
Re:What's Wrong with Jabber? (Score:1)
Re:What's Wrong with Jabber? (Score:2)
Re:What's Wrong with Jabber? (Score:1)
Just as well...Sun's enterprise servers are real crappy. Sun ONE = Sun (stock price in two years).
Re:What's Wrong with Jabber? (Score:1, Insightful)
Jabber's interface sucks (Score:2, Interesting)
The last version of Jabber I downloaded had an absolutely awful interface. It was usuable, although I think that for Joe Sixpack, it wouldn't be a serious option. I am quite computer savvy, (Java, PHP, Python, Perl, Linux, FreeBSD, Windows 2000) but I couldn't get to grips with it. The most popular system in South Africa seems to be MSN Messenger, followed by Yahoo Instant Messenger and ICQ's Messaging System.
Re:Jabber's interface sucks (Score:2)
Re:Jabber's interface sucks (Score:1)
What Interface? Jabber is a protocol. There are hundreds of interfaces you can have.
Well, that's kind of a problem in itself. But the interface I was talking about was the "main" Jabber distribution. (Sorry, it's been a while since I last tried it...) I am willing to give it another try, though, and will download later. The inter-protocol support and XML-based structure (if I remember correctly) was intruiging.
Re:Jabber's interface sucks (Score:1)
In Linux I use Gabber [sf.net].
Do you mean (Score:2)
I will say this though--
The documentation for jabberd 1.4.x could use some work. The first time I tried it, I could not get it to work, and only recently have I got things to work. I am hoping that this will improve with 2.0.x where all the work seems to be at the moment.
Re:Jabber's interface sucks (Score:5, Interesting)
I went through practically every Linux client I could find before finding one that I was happy with. Psi [sf.net] is a Qt-based client that acts and feels very much like the original ICQ client. No ads, sidebars, topbars, navbars, barbars... just a regular clean and simple IM client. There is [jabber.org] an extensive client list for Win32, Linux and MacOSX which lists the features of each. Psi works on all three, which is another reason I chose it. That, and the fact that, at the time, it was the only NON-Gtk client that looked half assed presentable and the ONLY Linux client that didn't take up a lot of screen real estate, and the ONLY Linux client that did NOT pop up the incoming message, stealing focus from whatever I was typing into.
Psi's Jabber client lib (and ssl comms) have been adopted by KDE for their IM clients too, which is a nice bonus.
Re:Jabber's interface sucks (Score:1)
The problem with multiple clients (Score:1)
The problem with having multiple clients is that although they may all start off using the standard Jabber protocol, if you want to call it that, they will eventually grow apart and some will have features that are exclusive to that particular client, and cause problems for people running other clients. This is why I would prefer a standard client distribution like MSN/ICQ/Yahoo have. (Although Jabber's more open nature, as well as it's ability to do inter-protocol messaging and integration, is a big bonus)
Re:The problem with multiple clients (Score:1, Interesting)
Yeah. Just look at email clients! We've got "standard" SMTP and ESMTP, but then every client just has to do it its own way. KSMTP, MS-SMTP, gSMTP, Lotus-SMTP, SMTP-XP, SMTP++, E-ESMTP, SMTP-Extreme...the list is endless!
Oh, wait. No, hang on thats not right. Every email client has actually managed to stick to the standar
Re:What's Wrong with Jabber? (Score:1, Interesting)
That's what's wrong with Jabber - the inconvenience caused by server outages.
Re:What's Wrong with Jabber? (Score:3, Informative)
Re:What's Wrong with Jabber? (Score:2)
Re:What's Wrong with Jabber? (Score:3, Informative)
Re:What's Wrong with Jabber? (Score:2)
Re:What's Wrong with Jabber? (Score:2)
Don't you mean GSSAPI / Kerberos?
Sure, LDAP allows having a single password checked against everywhere -- but it doesn't provide a means of passing around a single authentication token and thus only typing ones' password *once*.
Either way, Jabber is still lacking -- but IIRC, there's work on adding SASL support to Jabber, which in turn implies GSSAPI. I'll be happy when that's something stable enough to deploy.
irc? (Score:4, Informative)
Re:irc? (Score:1, Funny)
It doesn't matter... (Score:2, Interesting)
Re:It doesn't matter... (Score:1)
I hate microsoft outlook, but i have no choice to use it or not. My offices won't let me instlal another mail client and doesn't support imap... so what do I do?
They also don't use rational rose (morons), but I can't go install that eitehr, for my UML needs.
Re:It doesn't matter... (Score:2)
Doesn't do what you want and they won't let you use one you like? Do what I did - whip out your Platinum MasterCard, go to www.dell.com (or your preference) and under Small Business order yourself a machine. Have it delivered to your house. Instal
Re:It doesn't matter... (Score:5, Insightful)
heh, erm (Score:2, Insightful)
I cannot imagine this increasing productivity. really cannot. People will be able to interrupt your legitimate work from the convenience of their own cube! and I doubt you can hide yourself (invisible) because that would totally be against the whole point of INSTANT messenging.
And before people goes about and talk about monitoring your IM logs -
1
Re:heh, erm (Score:4, Insightful)
Looks like your experience is limited. Ever had coworkers more than a few cubicles away? I did, and instant messaging was quite a helpful tool. It is less intrusive and distracting than the telephone, especially if one has more than a single machine around. Doing software development, I use to have two machines on my desk, one for actual hacking and one for reading documentation, running tests, etc. -- and instant messaging.
Of particular importance to developers is the ability to easily exchange code snippets. Compare to reading them over the phone, or sending e-mail messages then waiting for a reply. IM gives instant access to coworkers' knowledge while making it easy to talk about technical matter that would be hard to express in voice.
And of course if you are serious about it you will allow people to make themselves unavailable.
Re:It doesn't matter... (Score:1)
Really I/my department use IM with some of our clients quite extensively. Communication systems are at their best when they can connect to other communcation systems - singuler they are useful but interconnected are powerful. Seeing as the current IM's don't interconnect they're not going to fulfil they're potencial.
Sun's messaging server is a bit late in the game and I doubt is going to be the one to unite them all. Jabber could bu
It's not for kids' chatting (Score:3, Insightful)
The data never leaves your private network, unlike Messenger, which routes everything through Redmond or wherever.
Cheers,
Jim
Re:It doesn't matter... (Score:2)
It doesn't matter how great the software is... frankly it's too late for a new entry. Because of network effects, messaging software is only as good as the number of people who already use it.
Sounds to me like a very good reason to use it, if you like it.
Market is wide open (Score:5, Insightful)
I read many comments like yours on Slashdot, and I can understand why you say that. For typical slashdotters, yes, Sun's announcement feels like too late. If you live in a major city in US or its metropolitan area, perhaps that's how you feel. If you work in the IT industry, more so. But the reality is that we are still at the beginning of the information age. I truly feel that the market is wide open.
If you look beyond US metropolitan area (and other, what they call, developed countries), there is a huge opportunity. There does not seem to be a wide margin in the IT industry in US, but there is China. There's large part of EU. Potentially, Middle East, now that Iraq war is pretty much over. Just that... it's over 5 times bigger that the whole US. Market is wide open.
In addition, Sun does have competitive edge over Exchange and Domino. The fact is that MS is stuck in the world of 32 bit. They say IA-64 is coming, but even if it arrives tomorrow, how long do they take to make it really functional AND get support from other ISVs? Domino is a competitive product, but Sun is really kicking IBM's ass in high end because of its quality, openness, and price.
I am not a marketing analyst and I cannot or dear not predict the future, BUT I do say that "... it's too late" sounds a little premature.
Re:Market is wide open (Score:2)
Sun appears to be marketing agressively in Asia. There is a whole version of StarOffice, called StarSuite, geared towards the asian markets. They also donate lots of software to asian countries trying to seed the markets there. I guess one advantage of being a global company is that there are alternatives now that the U.S. is in the dumper for the near future.
FFS! SUN needs to get with the Program!.. (Score:3, Funny)
This way they'll never get JoeSixpack to buy a single server!.. Come on!..
Re:FFS! SUN needs to get with the Program!.. (Score:2, Funny)
Or was it JoePack 6.0? Hmm...
Cost and offering (Score:4, Insightful)
With Sun: For a 100 person organsiation cost = $3000 + implementation time
With Jabber: implementation time
BIt of a no brainer?
Rus
Re:Cost and offering (Score:2)
SUN developed an entire suite of applications that integrate with each other. So Jabber isn't a contender in this particular case, if one chooses the rest of the suite that is.
Re:Cost and offering (Score:2)
Rus
Re:Cost and offering (Score:1)
The SOP is usually to get the vendor in asap to help when a system goes down. Since no vendor, hence no one to point the finger at. For a C-level exec, that's a Bad Thing(tm).
I think it's also that most large co
Re:Cost and offering (Score:1)
Do you know many CTO's and purchasing people?
on are more serious note it will probably be sold to those with existing Sun infrastructure and will augment it - they probably already have their market.
Re:Cost and offering (Score:4, Informative)
Jabber is only an IM service. Sun ONE is a whole enterprise collaboration environment. Comparing the two is like comparing KWord and Microsoft Office.
We need Open messaging (Score:5, Insightful)
They may not wish to rely on outside systems for internal communication but connections to outside IM systems may be essential. I won't lie I've not read the link yet. But my first though is how it would interact with other messaging systems.
The current biggies AIM, MSN, ICQ and Yahoo are no good as fragmented seperates - think back to BBS systems. Until they all sit down and decide to play together and use an Open standard it's not going to be as usefull as it could be. Untill then people will use what ever "frigs" they can to get them to interoperate such as Trillian (recommned the pro version by the way) or Jabbers connections.
Of course being HW focused if Sun push for an Open messaging standard touting their HW to power it all we could see some action but unfortunately they are a bit late in the game to weild that sort of power.
IM should interoperate and be as widespread as e-mail but it won't while everyone diggs in and backs their own standard.
.
Re:We need Open messaging (Score:2)
Or we could just all use IRC
Rus
Re:We need Open messaging (Score:2)
But as there was no central IRC body to 'market' it or be inclined to make it more attractive/inviting it would hve to be bettered/improved by someone else.
Once it becomes popular and accessible multiple approaches and implementations imerge. We then have large but fragmented userbases. Someone will push an interoperable system and the rest will have to join the fold or perish.
Not used GAIM but I should giveit a try. Like I
Re:We need Open messaging (Score:1)
I've been using it for a couple of weeks for ICQ, AIM, Jabber and IRC, and it's quite good, the interface is nice (needs a little polishing, but hey, it's still pre-1.0!). It's definately worth a look - and definately better than GAIM!!
Re:We need Open messaging (Score:1)
Forgot the darned 'http://'... Grrr...
Sun and version (Score:3, Insightful)
First the abrupt jump from Solaris 2.6 to Solaris 8, and now the first version of a new product is dubbed 6.0! Someone needs to smack the marketroids at Sun upside the head with the news that version numbers aren't just there because they make a pretty sound when you say them, they're meant to convey information to the customer. Sun's engineers seem immune to this, Solaris 8 still reports itself internally as SunOS 5.8, which kinda makes sense. Microsoft are Sybase are also guilty of doing it.
I can imagine the meeting now:
Marketer: Version 2 is better than 1 right?
Engineer: Sure
Marketer: And version 3 is better than 2?
Engineer: Umm, usually.
Marketer: Great! So the higher the number, the better the product!
Ah, I remember the good old days when Sun competed on technology, not hype. Most people I know are still running 2.6 in production, there's simply not enough new stuff in 8 to justify anything more than calling it 2.8, but while it's easy to get sign-off on a minor version patch, major versions need a lot more regression (on paper at least) and who's got the time for that?
Re:Sun and version (Score:5, Insightful)
Um, hello? That's exactly why this version number is 6.0. It's because it's not just a pretty sound when you say it, it is because it is meant to convey the concept that this IM product is meant to integrate with the SunONE platform, which, coincidentaly, has a version 6 label. Wild, isn't it?
-BrentRe:Sun and version (Score:1)
So what you're saying is, the version number of a product should be the same as the version number of its platform? Well, MS do that (Office 2000, SQL 2000 and so on) but they do write the whole lot, after all. By t
Re:Sun and version (Score:3, Informative)
http://wwws.sun.com/software/products/portal_ic
Redhat (Score:2)
Rus
Wrong (Score:4, Informative)
If you were at all familiar with RedHat versioning, you'd know that all revisions within a major version are binary compatible with each other, and major versions are not guaranteed to be binary compatible with each other. (Some may work fine, other binaries won't. Mostly this pertains to C++ apps, but in RH9, this pertained to anything that used threading.) RedHat decided that it was best for the distribution to move to a new threading architecture. It happened that this new threading system broke binary compatibility with RedHat 8.
As a result, consistent with RedHat's versioning policies, it was called RedHat 9.
I will admit that it does have a fringe marketing benefit, but the main reason for 9 was that it broke binary compatibility with RH8.
Re:Sun and version (Score:2)
For what it's worth, things went from 2.6 to 7 and up. SunOS is the operating system, Solaris is the 'operating environment', but you're right, in the end it is just numbers. It can't be easyt in the marketing department - for all the people who complain that the new numbering is 'hy
Re:Sun and version (Score:2)
BTW, UFS logging was available in Sol8 (Score:1)
Re:Sun and version (Score:2)
Just to pick nits, but the jump was from Solaris 2.6 to 7, not 8. SunOS went from version 4 to 'Solaris 2.4' So Solaris 2.4 is SunOS 4, Solaris 2.5 is SunOS 5, Solaris 2.6 is SunOS 5.6, though. I don't get it either.
I run 2.6 on my servers at work except for one because some clueless droid at Ford insists that I-DEAS 9.x MUST be served from a Solaris 8 server. (Ermm, yeah, whatever.)
There *are* differences. Most of those differences, however, invo
Re:Sun and version (Score:1)
Just to pick nits, but the jump was from Solaris 2.6 to 7, not 8. SunOS went from version 4 to 'Solaris 2.4' So Solaris 2.4 is SunOS 4, Solaris 2.5 is SunOS 5, Solaris 2.6 is SunOS 5.6, though. I don't get it either.
Actually, SunOS 4.x is the older, more BSD flavoured, version of their operating system. SunOS 5.x is the version of their operating system that we normally associate with the Solaris environment. So, Solaris 2.4 would be running SunOS 5.4, not SunOS 4. Solaris 2.5.1 ran SunOS 5.5.1, etc.
Re:Sun and version (Score:3, Informative)
Thanks for clearing that up.
Re:Sun and version (Score:1)
True, I should have spotted that. Solaris 7 was a bit of a funny one - very short lived, while Sun and Veritas argued over what exactly should be bundled and what should be paid for, and Solaris 8 was released as soon as they came to an arrangement. I've never come across Solaris 7 "in the wild" but I think I have CDs for it somewhere.
Re:Sun and version (Score:1)
I think you must have meant:
Solaris 2.6 -> Solaris (2.)7 -> Solaris (2.)8...
and so on. I guess Sun felt there would be no more major revisions and started using the minor rev as the release number.
--hc
DUH!
--hc
AIM Support (Score:1)
I don'
Re:AIM Support (Score:1)
AOL is not very interested in letting others jump on their protocol at this point. I'd assume that they are saving the functionality for their own coporate suite.
Real insightful, CowboyNeal (Score:5, Informative)
This should be alright...as long.. (Score:3, Informative)
As long as Sun goes with something like AOL compatibility for outside-the-intranet communication, they should be sitting pretty. Why would this even be necessary? Well the obvious is chatting with friends/family - without having to install a secondary client - but, also I know in my company we deal with outside agencies and businesses, and its much easier being able to IM them, than to send emails, or phone.
Also Messaging for Customers, Partners and Remote (Score:3, Informative)
My company could use this.
Of course to really see all the benefits you will want to use the other components as well which all use Liberty spec and SAML (Security Assertion Markup Language) for completely single sign on to messaging (e-mail), calendaring, instant messaging and web portal / content management.
Remember that this is just the latest incarnation of iPlanet.
feh (Score:1, Insightful)
Future Sun Commercial (Score:1, Funny)
TheBoss: How did our trade secrets get out? I'm calling for a full investigation!
Employee: Maybe it's because we use AOL for our chat and they receive everything we send!
TheBoss: What? Quick! Get a Sun ONE Server!
Thank goodness. (Score:2, Funny)
zwrite (Score:1)
So I read a bunch of the replies.. wtf? (Score:3, Interesting)
It's not about SUN making IM softare. It's about their IM/Collaboration/Calendar/Email suite. It's about them releasing software, that integrates well with their software. Being redundant there. It's about cool little popups from their IM program telling you about a meeting or about email, muchlike yahoo client does
If you wanna keep talking about Jabber Protocol, why not SOAP, or XML-RPC? Cripes... As if that's what the article really is about.
Domino? Please (Score:4, Interesting)
Anyone who has ever used Domino's document management tools or developed an application for Notes knows exactly what I mean. You have the ability to develop highly advanced applications, not just folders full of sticky notes (e.g. Exchange). You don't have filing cabinets full of sticky notes, do you? Why should your database?
The biggest disadvantage of Domino is the fact that developing for it is kind of its own little world. I'm looking forward to Domino R7's integration with WebSphere. But even until then, Domino gives you a document management development environment second to none.
The weird thing is that the feature that everyone looks at Domino most closely for, e-mail, is its weakest point. That's what comes from building e-mail around a document-mangement platform, instead of building document management around an e-mail platform.
lemme guess (Score:2)
FINALLY! (Score:3, Funny)
Re:Jabber (Score:1)
Re:Jabber (Score:5, Insightful)
There are libraries that let you write integration code for any program you have. Search CPAN for Jabber and you'll see what I mean.
Can I interface Sun's product with my company's homebrew scheduling system and the online shop I wrote? I know that I can with Jabber.
Jim
Re:Jabber (Score:1)
Jabber just wont fit.
Re:Jabber (Score:2)
I would choose an option that offered fewer initial features, but completely open standards. At least then, I'm not relying upon the vendor for functionality.
Re:Bah, another shot in the foot (Score:1)
A hella' lot more.
Re:Bah, another shot in the foot (Score:1)
1. Builds 4x AMD Multiproc boxes himself
2. Installs Linux, Jabber as 2 box cluster w/ a fail over 2 box cluster
3. Waves the b-s flag about stability, knowing all the while it doesn't matter what you have if you are a competent admin/ admin team, Murphy's Law isn't picky.
4. Saves a buncha cash vs those proliants
5. Has the added benefit of not having to deal with a Microsoft software lock in.
6. Uses the money to by a hell box to serve Doom3 on.
Anyone who has to buy their pr0n just doesn't get i
Re:Chatting (Score:2)
Re:Chatting (Score:1)
Do you have any idea what jabber is?
this is a lie (Score:1, Funny)