Slashdot Mirror


Sun Launches Instant Messaging Server

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.

172 comments

  1. What's Wrong with Jabber? by redcliffe · · Score: 4, Interesting

    You can run your own Jabber server, and it can also message other Jabber users. Some of the clients support encryption too.

    1. Re:What's Wrong with Jabber? by the+uNF+cola · · Score: 5, Informative
      Jabber doesn't integrate with sun's other enterprise utility servers.


      The platform, which consists of several separate server packages -- Sun ONE Messaging Server, Sun ONE Instant Messaging, Sun ONE Portal, Sun ONE Calendar Server, and Sun ONE Identity Server -- is available now and takes aim at rivals Microsoft and IBM/Lotus in the lucrative collaboration arena, said David Ferris, analyst with Ferris Research.


      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 :)
      --

      --
      "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

    2. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 1, Insightful

      But Jabber doesn't come with glossy sales brochures and pointed marketing bullshit. Jabber won't 'increase the productivity of your workforce by upto 100000000%', or 'integrate flawlessly with our task management and collaboration framework', or.... you get the idea.

    3. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 1, Interesting

      I use Gabber under Solaris for MSN and ICQ. Sometimes they have outages on one of the Jabber services for hours. It's really annoying not being able to access MSN from my Sun box when I need it for work, it's a little inconvenient having to load up MSN Messenger under my SunPCI Windows installation mainly because I have the speaker output plugged into the Sun box (rather than the PCI card)

      That's what's wrong with Jabber - the inconvenience caused by server outages.

    4. Re:What's Wrong with Jabber? by redcliffe · · Score: 3, Insightful

      Yes, but what's wrong with using it's protocol. Jabber is a protocol, not a program. Interoperablity is always a good thing.

    5. Re:What's Wrong with Jabber? by redcliffe · · Score: 2, Informative

      If you've got your own Jabber server, then it's your fault if it goes down. That's the whole point, the server is freely available to download, I could run one on my LAN if I wanted to.

    6. Re:What's Wrong with Jabber? by PhiberOptix · · Score: 0

      besides the reason uNF cola gave, Jabber also isnt out of the box "LDAP ready". (from what I read, i may be wrong). And LDAP is prerequisite to having a single sign-on implementation.

    7. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 0

      You make a good point, however:

      - I don't have my own Jabber server, I use jabber.org.uk

      - I really don't think it's worth running my own jabber server if I'd be the only one in the company using it

      - I probably wouldn't be allowed to anyway ;-)

    8. Re:What's Wrong with Jabber? by Organic_Info · · Score: 1

      Yeah well until they all unite behind a single open protocol and integrate together its going to stay as fragmented as the old BBS systems were.

      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.
      .

      --
      "Things that you own end up owning you" - Tyler Durden (via Diogenes of Sinope).
    9. Re:What's Wrong with Jabber? by redcliffe · · Score: 1

      Again. Jabber is a protocol, not a program. Therefore a daemon could be written using the Jabber protocol that used LDAP to authenticate.

    10. Re:What's Wrong with Jabber? by PhiberOptix · · Score: 0

      youre right. I thought that if Sun used Jabber its software would have to be GPLed, but that doesnt seem to be the case as it seems there are many "commercial jabber servers" available.

    11. Re:What's Wrong with Jabber? by Bake · · Score: 1

      If you really want to access MSN from your Sun box I suggest that you try GAIM (It's not just for AOL, kids!).

    12. Re:What's Wrong with Jabber? by hpavc · · Score: 2, Insightful

      There isnt anything wrong with it that I have ever found. Its easy to extend and scale and making a client is very easy and can be as sexy as you want or need it to be (c, java, .net, perl)

      Not that its proof of anything but Oracle has gone down this path as well on the integrated IM services.

      --
      members are seeing something, your seeing an ad
    13. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 0

      It's like wanting jabber to integrate with yahoo mail and yahoo calendar, along with the privacy.

      That's a great idea. There should be an open protocol for calendar, address book, etc. An open protocol on these items would spawn MS Exchange replacements fairly rapidly. Couple the calendar, address book, a mail server, and a jabber server in an open source cross platform server, that's exciting to think about.

    14. Re:What's Wrong with Jabber? by kevlar · · Score: 2, Insightful

      If you're going to use the protocol argument, then you should stick with the IETF's SIMPLE protocol.

    15. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 0

      Jabber is not free software. It's a protocol.

      Perhaps you meant that jabber sucks because its clients are free, which is also not true. Many clients are free, but there are commercial ones as well.

    16. Re:What's Wrong with Jabber? by Wille · · Score: 1


      If you want a quick jabber server setup you should look at JabberD Quickstart

      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. :)

    17. Re:What's Wrong with Jabber? by rgraham · · Score: 2, Informative

      If you go to Jabber.org you'll see there has been a lot of large investments/installations of the Jabber protocol (usually from Jabber Inc.) recently, from companies like Intel, France Telecom, EarthLink, etc. So I think headway is being made, but there aren't large annoucements being made that Joe AOL user would notice. And maybe that is where the problem is. When a city government I was contracting for was looking for an instant messenger solution I instantly suggested Jabber, since I had worked with both the open-source Jabberd and Jabber Inc servers. Fortunately, with Jabber Inc being a local company (I live in Denver) getting them to come out and show-off their wares wasn't a difficult thing to do. But, I'm sure that outside of my boss at the time, very few, if any, of the city's IT people were aware of Jabber and were all probably thinking AOL, MSN, Yahoo!, whenever the topic of IM came up.

    18. Re:What's Wrong with Jabber? by einhverfr · · Score: 4, 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.

      --

      LedgerSMB: Open source Accounting/ERP
    19. Re:What's Wrong with Jabber? by demaria · · Score: 2, Informative

      Jabber (from the commercial Jabber company, not the generic protocol) has a server user interface that makes sendmail configs look fun, no polls, no surveys, no screensharing, no whiteboard and no moderated chat rooms. Sun has all of those, and some are very useful.

    20. Re:What's Wrong with Jabber? by sporty · · Score: 2, Interesting

      It doesn't integrate with sun's suite. The problem IS jabber. It won't work with software someone MAY want.

      That's like blaming MS for not using Linux's drivers. They don't work together.

      --

      -
      ping -f 255.255.255.255 # if only

    21. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 0

      EarthLink is using Jabber in house. Not sure if they have plans to extend this to a customer offering or not.

    22. Re:What's Wrong with Jabber? by einhverfr · · Score: 2, Interesting

      It doesn't integrate with sun's suite. The problem IS jabber. It won't work with software someone MAY want.

      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 than IP :-P

      The point is I see no reason why an Exchange connecter could not be written to allow a groupware client to access calendar, email notifications, etc. via the Jabber protocol. It would probably be relatively easy to do. Same with any other server that has an SDK associated with it. This connector could be a jabber client itself, or could be a plugin to a jabber server (and act as a gateway).

      Jabberd today integrates with MSN, Yahoo, ICQ, AOL, SMTP(!) etc. and also can provide many other services.

      --

      LedgerSMB: Open source Accounting/ERP
    23. Re:What's Wrong with Jabber? by np_geek · · Score: 1

      Or once you;ve got it up and running there's even a Jabber module included in a default Webmin install: http://www.webmin.com/standard.html Doesn't get a whole lot easier than Webmin.

    24. Re:What's Wrong with Jabber? by andy1307 · · Score: 1
      Jabber doesn't integrate with sun's other enterprise utility servers

      Just as well...Sun's enterprise servers are real crappy. Sun ONE = Sun (stock price in two years).

    25. Re:What's Wrong with Jabber? by sporty · · Score: 2, Insightful
      It doesn't integrate with sun's suite. The problem IS jabber. It won't work with software someone MAY want.


      What Jabber are you referring to? the core protocol or the many proprietary or opensource implimentations?


      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 they did, they'd have to modify it to their whims and close source it anyway, since they probably won't offer support contracts for opensource software they didn't write.


      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 than IP :-P


      No, it's like using analogies to say what you really mean. Jabber doesn't integrate with the whims of Sun for whatever reason they know of. Does jabber protocl support calendar's and email notifications better than something sun cooked up? Do the jabber clients out there (which I doubt they'd use) support the functions they want? It's a right fit issue, not a "it's crap or not" issue.

      The point is I see no reason why an Exchange connecter could not be written to allow a groupware client to access calendar, email notifications, etc. via the Jabber protocol. It would probably be relatively easy to do. Same with any other server that has an SDK associated with it. This connector could be a jabber client itself, or could be a plugin to a jabber server (and act as a gateway).


      because they don't see it fit. For instance, why don't i use the jabber protocol for DNS? It's too heavy. A UDP packet is a LOT smaller than a bunch of tcp packets carrying jabber.

      Jabberd today integrates with MSN, Yahoo, ICQ, AOL, SMTP(!) etc. and also can provide many other services.


      As much as jabber is a great protocol and all, when you have a hammer, everything looks like a nail.

      --

      -
      ping -f 255.255.255.255 # if only

    26. Re:What's Wrong with Jabber? by einhverfr · · Score: 1

      No, it's like using analogies to say what you really mean. Jabber doesn't integrate with the whims of Sun for whatever reason they know of. Does jabber protocl support calendar's and email notifications better than something sun cooked up? Do the jabber clients out there (which I doubt they'd use) support the functions they want? It's a right fit issue, not a "it's crap or not" issue.

      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 Jabber advocacy rather than Sun-bashing. Jabber is an immensely powerful idea. But the real point is not the merits or lack thereof regarding Jabber but the fact that we do not have an open-source enterprise-level groupware solution available. This is the issue. I think that Jabber would be an immensely useful part of such a solution (as would LDAP, calendar management, IMAP, etc).

      Sun can do what they want. That is there perogative....

      --

      LedgerSMB: Open source Accounting/ERP
    27. Re:What's Wrong with Jabber? by rgraham · · Score: 1

      You're right, I haven't heard if they are going to start including a Jabber client for subscribers, and there again is part of the problem. Jabber is being used, but its just not real visible. I know AT&T uses Jabber a lot, not just for person to person IMing, but to monitor various pieces of equipment, servers, routers, etc.

    28. Re:What's Wrong with Jabber? by boskone · · Score: 1

      I think it would be more like like saying that win98 doesn't support DECNET. A less used (but still important) protocol that isn't necessarily clearly superior to the other options available.

      It was just a design decision, not a religious decision to not use Jabber's protocol IMHO.

    29. Re:What's Wrong with Jabber? by bob291 · · Score: 1

      You opened up an interesting question that I have been pondering for some time. Why is there not an effort to provide an open source enterprise groupware server? I think this should be asked to the larger slashdot community as a new thread.

    30. Re:What's Wrong with Jabber? by cduffy · · Score: 1

      No, it's like using analogies to say what you really mean. Jabber doesn't integrate with the whims of Sun for whatever reason they know of. Does jabber protocl support calendar's and email notifications better than something sun cooked up? Do the jabber clients out there (which I doubt they'd use) support the functions they want? It's a right fit issue, not a "it's crap or not" issue.

      Jabber doesn't need to explicitly support calenders and email notification any more than the IP standard needs to have a section regarding online gaming -- if that calender and email notification system is appropriately described by a publish/subscribe model, it can be run over the Jabber protocol.

      Thing is, you're still thinking of Jabber as an application or a special-use protocol. It isn't. Jabber is extremely generic, much as TCP is generic; whether one builds an RPC mechanism or a stock ticker or a tool for notifying servers that it's time to install a new build or whatever is irrelevant. If your application is appropriate for the Jabber protocol -- and messaging, calendaring and email notification are things it's remarkably good for -- then you're reinventing the wheel by not using it. Within the space of presence notification and publish/subscribe, one can attach info conforming with any XML namespace one wants to the message -- so if the existing, standardized ones don't work, make your own. Similarly, integrating with preexisting systems requires relatively little work because there's a protocol for writing serverside plugins to impliment almost any reasonable functionality on top of the core Jabber protocol -- a core protocol which is almost universally usable within the scope of a messaging application.

      Of course, I'm not claiming Jabber is appropriate for everything -- your example regarding DNS is a reasonable counterexample. DNS is a very different thing from a messaging/calendering/etc server, however; Jabber is indeed a poor fit for the former space, while it's damn near perfect for the latter.

      Some of your questions are even self-answering. If they're not using the clients out there, whether those clients support some namespace they cook up for their own calendering solution is irrelevant, and if they're implementing their own namespace for it then it doesn't matter how well whatever analogous standardized namespace fits their needs. (Of course, if they *could* stick with the standards on that, it makes their work that much easier -- but let's say that they have some good reason to reinvent that portion of the wheel). There's still no good reason to impliment any kind of messaging system without taking a good hard look at Jabber.

    31. Re:What's Wrong with Jabber? by cduffy · · Score: 1

      And LDAP is prerequisite to having a single sign-on implementation.

      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.

    32. Re:What's Wrong with Jabber? by e2d2 · · Score: 1

      Although SIMPLE is making much headway there are other protocols such as SNPP, SMPP, and IMPP that are just as far along in the IETF standardization process. BUT that being said SIMPLE is the agreed to standard that both AOL and MSN have agreed to use. MSN currently can use SIMPLE and AIM has plans to add SIMPLE support because that was part of the deal with the FCC when the merged with TIme Warner. And SIMPLE is based on SIP, which has huge support amongst Network and Telephony vendors such as Cisco and Nokia.

      But it is still up in the air as to which protocol will dominate. SIMPLE, SNPP, SMPP, IMPP, Jabber, SMS. ehh gads thats a huge cluster f**k.

      DIUALOAA: damn I used a lot of acronyms above

    33. Re:What's Wrong with Jabber? by Anonymous Coward · · Score: 0

      I'm fairly sure the Sun IM server uses an open protocol called CPIM (although this isn't substantiated). This is an older IETF standard that is being supplanted by XMPP (IETF name for Jabber) and SIMPLE. Interestingly, there is already a standard way to map CPIM to XMPP: http://www.ietf.org/internet-drafts/draft-miller-x mpp-cpim-00.txt

    34. Re:What's Wrong with Jabber? by einhverfr · · Score: 1

      Hi Bob-- I I am looking at what would be involved in this sort of setup. Send me an email if you want and maybe we can look at what can be used for this sort of issue.

      --

      LedgerSMB: Open source Accounting/ERP
    35. Re:What's Wrong with Jabber? by sporty · · Score: 1

      Some of your questions are even self-answering. If they're not using the clients out there, whether those clients support some namespace they cook up for their own calendering solution is irrelevant, and if they're implementing their own namespace for it then it doesn't matter how well whatever analogous standardized namespace fits their needs. (Of course, if they *could* stick with the standards on that, it makes their work that much easier -- but let's say that they have some good reason to reinvent that portion of the wheel). There's still no good reason to impliment any kind of messaging system without taking a good hard look at Jabber.


      You are assuming they haven't. If they did, then they obviously found something "better". What about SOAP, XML-RPC? What if they are using something that's NOT XML, like EJB or RMI (one uses the other, I know).
      --

      -
      ping -f 255.255.255.255 # if only

    36. Re:What's Wrong with Jabber? by raxhonp · · Score: 1


      What about SOAP, XML-RPC?

      That's indeed a good question:
      - JEP-0009: Transporting XML-RPC over Jabber
      - JEP-0072: SOAP Over Jabber

  2. Bah, another shot in the foot by Flak · · Score: 0

    *installs linux on AMD chip

    *installs Jabber

    *saves 10k

    *buys sweet rig and waits to host doom3

    1. Re:Bah, another shot in the foot by the+uNF+cola · · Score: 1

      Cost to pay developers to get it to integrate with lotus or MS collaborative stuff (notes i.e.)

      A hella' lot more.

      --

      --
      "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

    2. Re:Bah, another shot in the foot by Anonymous Coward · · Score: 0

      or:

      1. Buys 2xHP proliants
      2. Installs Domino and sametime on NT4/2k as a cluster
      3. observes nearly 5 nines stability (or at least it is where I work)
      4. Saves a bunch of cash
      5. Has the added benefit of not having to deal with a sun hardware lockin.
      6. Uses the money saved to buy pr0n, and lots of it.

    3. Re:Bah, another shot in the foot by cHiphead · · Score: 1

      once again...

      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 it, or is a terrorist.

      --

      This is my sig. There are many like it, but this one is mine.
  3. irc? by terminal96 · · Score: 4, Informative

    we have a company irc server where i work. works well enough.

    1. Re:irc? by Eric+P.+Henus · · Score: 1, Funny

      @find *spice*girls*bootleg

  4. It doesn't matter... by ajuda · · Score: 2, Interesting

    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.

    1. Re:It doesn't matter... by the+uNF+cola · · Score: 1

      It does matter. This is for a company to use internally.

      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.

      --

      --
      "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

    2. Re:It doesn't matter... by JaredOfEuropa · · Score: 4, Insightful

      That hardly matters for corporate users, at whom this product is aimed. The idea is that employees use it mainly for interoffice messaging, not yapping all day to their pals.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    3. Re:It doesn't matter... by shivianzealot · · Score: 1

      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.

      --

      Bored with karma, be a fan/freak

    4. Re:It doesn't matter... by Organic_Info · · Score: 1

      "That hardly matters for corporate users, at whom this product is aimed."

      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 but there are not enough heavyweight playes or large enough userbase behind it. Now if IBM started deploying interoperable Jabber messaging servers....

      Who evers pushes interoperability will win.
      .

      --
      "Things that you own end up owning you" - Tyler Durden (via Diogenes of Sinope).
    5. Re:It doesn't matter... by Glonoinha · · Score: 1

      Hate is such a strong word. Honestly if the software does what you need it to do (serve and deliver email) then use it and get on with business. There is no work related email needs at your company that Outlook can't handle or they would issue something else.

      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. Install whatever OS, tools, programs, games, warez, pr0ns, unsupported sound and video cards, and imap email client you want on it and after all the PHBs have left for the day (mind-bendingly close to 5pm, for sure) walk the damn thing right in the front door. Put it under your desk and hook up the 2 port KVM you bought for $50 so you can swap back and forth between machines on your work keyboard, monitor, and mouse. Plug it into the network and get a DHCP connection to the outside world (you generally don't even need to be part of their domain to snag an IP address and an outside connection via their network) and Bingo! you are home free and productive beyond your wildest dreams.

      All for about $500 - you could probably even expense account the thing over the next six months and not get questioned.

      As for Rational Rose - install it on that machine and have a good time. You don't need permission to install software on a machine they don't even know exists.

      New computer : $500
      Linksys 2 port KVM : $50
      Warez copies of the software you really want to run : $0
      Happily working in the (virtual) environment you like : Priceless.

      -:-

      As for Sun coming up with a new IM server / scheme / program ... about damn time. God knows of all the productive things they could have been inventing what the world needs right now is yet another Instant Message tool. Because IM software is so fscking profitable right now and there are only a dozen existing tools to choose from including the one that installs (free) on every WinXP machine on the planet.

      Jesus - why doesn't Sun announce they are also coming out with a web browser while they are at it.

      Merging Solaris and Linux is good. Good job on that.

      Sun - here is what we want :
      Most of the people here have multiple machines at their disposal. Give better ways to cluster them into one big virtual SMP machine. Yea I know about Beowulf but ... no - that is exactly what we want. Take Beowulf and make it run on multiple machines .. no wait - it already does that. Ok, how about make Beowulf run on Linux (wassat? already does?) Crap. Ok - how about take Beowulf on a bunch of machines and make it better - Blade servers are coming out in force, end users are able to buy half a dozen machines for what one used to cost ... give us a way to leverage all this super cheap hardware and apply it to a single task. And work well. As a single entity.

      Now THAT would be a way better use of your development efforts than a new IM app.

      --
      Glonoinha the MebiByte Slayer
  5. Re:Jabber by the+uNF+cola · · Score: 1

    Integrate with sun's other services, which will compete with MS and Lotus collaboration suites? Jabber only does IM, which is great and all, but doens't integrate on those levels.

    --

    --
    "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

  6. It's not for kids' chatting by wirefarm · · Score: 2, Insightful

    This is a server that you run in an office, not a competitor to ICQ and Yahoo.
    The data never leaves your private network, unlike Messenger, which routes everything through Redmond or wherever.

    Cheers,
    Jim

    --
    -- My Weblog.
  7. Jabber's interface sucks by nigel.selke · · 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.

    --

    We hang the petty thieves, but appoint the great ones to public office. - Aesop

    1. Re:Jabber's interface sucks by Anonymous Coward · · Score: 0

      So you downloaded Jabber itself then and not one of many jabber client?

      Freak!

    2. Re:Jabber's interface sucks by redcliffe · · Score: 1

      What Interface? Jabber is a protocol. There are hundreds of interfaces you can have.

    3. Re:Jabber's interface sucks by nigel.selke · · 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.

      --

      We hang the petty thieves, but appoint the great ones to public office. - Aesop

    4. Re:Jabber's interface sucks by Anonymous Coward · · Score: 0

      http://psi.sf.net

    5. Re:Jabber's interface sucks by tzanger · · Score: 4, Interesting

      I went through practically every Linux client I could find before finding one that I was happy with. Psi 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 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.

    6. Re:Jabber's interface sucks by Anonymous Coward · · Score: 0

      What Interface? Jabber is a protocol. There are hundreds of interfaces you can have.

      Well, that's kind of a problem in itself.


      Yeah, just like tcp/ip, ftp, smtp and other protocols are a problem in and of themselves... jeez.

    7. Re:Jabber's interface sucks by wossName · · Score: 1

      If you're using Windows, Exodus is a pretty nice Jabber client. Miranda is also excellent, it's an ICQ client, but with tons of plugins (and you can even turn ICQ off). Get Miranda's latest Jabber plugin.

      In Linux I use Gabber.

      --
      Someone is wrong on the Internet!
    8. Re:Jabber's interface sucks by lscotte · · Score: 1

      I second the suggestion to try psi. I've tried every Linux client I could find, and like psi the best. It's not completely perfect and polished, but overall it works nicely.

      --
      This post is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License.
    9. Re:Jabber's interface sucks by Anonymous Coward · · Score: 0

      "...and the ONLY Linux client that did NOT pop up the incoming message, stealing focus from whatever I was typing into."

      Wow. Jesus. Windows has had that UI bug fixed for ages now (since Windows 2000, IIRC.) Windows now blink on the system tray instead of stealing focus.

      It's stuff like this that Linux still doesn't have and may NEVER have because Linux programmers are not focused on usability. That is a classic example of why most people would not want to use Linux on the desktop in its current state. Ugh. And for you to say that you wanted a program that was missing features in order to work around a usability issue... wow. That is truly sad.

    10. Re:Jabber's interface sucks by Anonymous Coward · · Score: 0

      We have a new Jabber client that has most of the features you liked about psi, plus some additional features such as tabbed chat window, typing indicator, customizable toolbar, etc. It is also based on Qt and cross platform. You can download it from www.akeni.com

  8. FFS! SUN needs to get with the Program!.. by Anonymous Coward · · Score: 3, Funny
    Dubbed 'Sun ONE Instant Messaging 6.0,'
    That is _so_ 90's!! They should have called it Sun ONE Instant Messaging XP or MX or something..
    This way they'll never get JoeSixpack to buy a single server!.. Come on!..
    1. Re:FFS! SUN needs to get with the Program!.. by slashd'oh · · Score: 2, Funny

      Don't you mean joesiXPack? That's the new title for our sysadmin who buys all of our servers.

      Or was it JoePack 6.0? Hmm...

  9. Cost and offering by rf0 · · Score: 3, Insightful

    So this costs $30 per user and no mention of the client software requirements. Will they just be Solaris or Linux/Windows/Solaris? As other people have said why not just role out jabber?

    With Sun: For a 100 person organsiation cost = $3000 + implementation time
    With Jabber: implementation time

    BIt of a no brainer?
    Rus

    1. Re:Cost and offering by Diabolical · · Score: 1

      Like the reply to the previous poster; Integration

      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.

    2. Re:Cost and offering by rf0 · · Score: 1

      Can't argue with that. Also companies might want the support that can be offered from a commerical company. A mentalitity I've noticed is that companies don't think support is decent unless you pay for it. I thing that the mailing lists for things normally do fill this need but don't necessarily offer that someone will actually get an answer

      Rus

    3. Re:Cost and offering by Anonymous Coward · · Score: 0

      It's reasonably lightweight Java client and works very nicely.

      With Sun: For a 100 person organisation cost= $3000 + implementation time, polished product with roadmap, interoperates with other Sun ONE products and LDAP directories beautifully, fully supported, large number of supported well documented features, etc, etc.

      With Jabber: Implementation time, free, no support, no roadmap, usual arguments for and against.

      Bit of a no brainer? When you have to support 1000s of users using an IM system, the last thing you're going to choose is Jabber.

    4. Re:Cost and offering by Organic_Info · · Score: 1

      "As other people have said why not just role out jabber?......BIt of a no brainer?"

      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.

      --
      "Things that you own end up owning you" - Tyler Durden (via Diogenes of Sinope).
    5. Re:Cost and offering by Henry+Stern · · Score: 3, Informative

      $3000 for 100 users is not only on par with the competition, but is small potatoes. A few years ago, I helped with a Domino/Notes/Sametime rollout where the server software before the CALs was well over five figures.

      Jabber is only an IM service. Sun ONE is a whole enterprise collaboration environment. Comparing the two is like comparing KWord and Microsoft Office.

    6. Re:Cost and offering by salemnic · · Score: 1

      I think it's a bit more than that. Companies want someone they can point the finger at in an emergency and say FIX IT!!!!!!!! It's also a liablility thing. That's why most companies need an outside consultant to say exactly what their IT people have been saying before they'll go ahead with it.

      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 companies already have a relationship with Sun that gives them a warm and fuzzy when they buy from Sun. That really applies to the other big vendors as well, I suppose.

      What this boils down to is that a lot of big companies have a NO FREEWARE!!!!! edict that comes down from above.

      Cheers,

      S

    7. Re:Cost and offering by imadcow1 · · Score: 1

      Jabber is only an IM service. Sun ONE is a whole enterprise collaboration environment. Comparing the two is like comparing KWord and Microsoft Office.

      But would most not use KWord (the word processor) more often than the entire Microsoft Office suite (word processor, presentation program, spreadsheet etc.)? And wouldn't most use instant messaging (Jabber) more than SunOne (instant messaging with many other collaborative features)?

  10. Re:Jabber by wirefarm · · Score: 4, Insightful

    The appeal to me is that Jabber is an open standard with well thought out open protocols. Anyone can write their own Jabber client in any language. Same for interfaces.

    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

    --
    -- My Weblog.
  11. We need Open messaging by Organic_Info · · Score: 4, Insightful

    "for businesses which don't wish to rely on an outside network for their messaging"

    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.
    .

    --
    "Things that you own end up owning you" - Tyler Durden (via Diogenes of Sinope).
    1. Re:We need Open messaging by rf0 · · Score: 1

      For cross communication I belive that only AOL/ICQ work. The nearest I've really seem to come to cross network is using gaim as client which at least allows me to see other peeps in one window rather than having to run 3 or 4 different messaging programs

      Or we could just all use IRC

      Rus

    2. Re:We need Open messaging by Organic_Info · · Score: 1

      I wondered why IRC did not hold its ground (grow) as the original widely used IM.

      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 said though Trillian does a good job. I've had less experience with Jabber but that has potential.

      --
      "Things that you own end up owning you" - Tyler Durden (via Diogenes of Sinope).
    3. Re:We need Open messaging by vofka · · Score: 1

      Try Kopete (Project Homepage), it's a KDE/Qt based IM Client, which does Jabber, ICQ, AIM, MSN, IRC and a couple of less well-known's. It uses a plug-in based architechture, so adding new protocols is as easy as writing a plugin. (!)

      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!!

      --
      Disclaimer: I meant what I thought, not what I wrote! What? You can't read my Mind? Oh dear!
    4. Re:We need Open messaging by vofka · · Score: 1

      Better still: Try this for the project homepage

      Forgot the darned 'http://'... Grrr...

      --
      Disclaimer: I meant what I thought, not what I wrote! What? You can't read my Mind? Oh dear!
  12. The problem with multiple clients by nigel.selke · · 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). Perhaps if they created a standard client distribution, and created a superior interface for it, Jabber would take off amoung the masses. Until then, it looks doubtful that it will enjoy success that MSN, ICQ and Yahoo have.

    --

    We hang the petty thieves, but appoint the great ones to public office. - Aesop

    1. Re:The problem with multiple clients by Anonymous Coward · · Score: 1, Interesting

      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...

      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 standards (Bar implementation errors, of course). Wow, how did they possibly manage such a complex feat? The world is an amazing place!

      it looks doubtful that it will enjoy success that MSN, ICQ and Yahoo have

      Jabber is fast on its way to becoming an Internet Standard (Or at least the basis for a standard) for Instant Messaging. A cross platform, cross client, open standard.

      Please stop talking about Jabber as though you know what it is. Donwloading it once does not make you an expert (Neither am I, but I have a slightly better grasp on the basic issues than you do, it seems).

      I hate Slashdot sometimes.

    2. Re:The problem with multiple clients by Anonymous Coward · · Score: 0

      He's a drongo, for sure. "Jabber protocol, if you want to call it that." Well, yeah, fucktard, given that's what it is.

      http://www.scbd.connectfree.co.uk/flops/nice-sou th -african.html

  13. Chatting by craesh · · Score: 0

    Hey, I thought it's not allowed to chat while you're working.

    But I'm wondering who will need it. I mean, here where I work we just call each other if we want to talk or have questions. Its faster, you can type or do whatever while you're talking to someone.

    And if you really need an IM-System, then why not use Jabber? It's free, and there are a lot of clients for different platforms and needs.

    craesh

    1. Re:Chatting by torqer · · Score: 1

      IM at work definately has it's uses. Picking up the phone and calling isn't usually worth it when you are trying to reach someone long distances (or overseas for that matter). Ever been on a conference call and have someone put the whole call on hold so he can talk to someone else? Nothing like hold music stopping the entire call while buddy talks to the other person. Why not use Jabber? Because Sun's offering is designed for IMs to people with in the company. It's secure, It's not over the internet, and it intergrates with other Sun products.

    2. Re:Chatting by duffbeer703 · · Score: 0

      Why don't you get a clue before posting?

      Do you have any idea what jabber is?

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
  14. Sun and version by sql*kitten · · Score: 3, Insightful

    the first part of its new enterprise collaboration platform to compete with Exchange and Domino. Dubbed 'Sun ONE InstantMessaging 6.0

    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?

    1. Re:Sun and version by bmetzler · · Score: 5, Insightful
      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.

      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?

      -Brent
    2. Re:Sun and version by christophersaul · · Score: 1

      There's a large number of reasons to move to 8/9, not least the ability to run on the new UIII systems from 8 upwards, have a journalling, high performance file system in 9 and various other goodies. Sun.com has a good list.

      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 'hype', which is a little extreme a criticism, you'd have another lot complaining the old numbering made Sun look 'old', had it been kept.

    3. Re:Sun and version by sql*kitten · · Score: 0

      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?

      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 that argument, since it runs on Solaris 8, maybe they should have called it "Messaging 8.0"?

      It's 1.0, and there's a good reason that people shy away from version 1.0 of products. Sun are just trying to pretend that it's already as mature as some of their other products. It's a marketing scam, nothng more.

    4. Re:Sun and version by Surak · · Score: 1

      First the abrupt jump from Solaris 2.6 to Solaris 8,

      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, involve stuff we don't use or even need. :)

    5. Re:Sun and version by sirinek · · Score: 1

      Yeah but slashdot is littered with people who know nothing about any type of enterprise systems, just Windows and Linux, and so make lame comments based upon no real facts at all whenever they hear something about Solaris, HPUX, AIX, Tru64, etc etc.

    6. Re:Sun and version by Anonymous Coward · · Score: 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.


      Actually, someone needs to smack you upside the head with the news that version numbers nowadays hardly convey any substantive information at all, but rather are chosen almost purely for marketing purposes.

      Just a few examples: After Windows 3.11, Microsoft stopped using incrementally rising version numbers for their Windows product altogether. Since then they've had Windows 95, Windows 2000, Windows XP and so forth. And remember that was never any 5.x version of Netscape at all? They went from Netscape 4.7 or whatever it was to 6.0, mainly because Explorer was already into 6.x. And Netscape 6.x was only on the market for what seemed like a couple of weeks, now they're already into 7.x.

      Of course this is all ridiculous, but the sad fact is that marketdroids only do this kind of thing because it actually works. Given a choice between WhizBang 5.0 and Bells&Whistles 6.0, some people really will have a tendency to think that the product with the higher version number is better; and this bias might even be strong enough to outweigh the other merits of the products. Sorry to say it, but human beings really can be that stupid sometimes, and marketers will not hesitate to take advantage of the fact.
    7. Re:Sun and version by CapeBretonBarbarian · · 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. Note that Sun did eventually rename the older SunOS 4.x operating environment Solaris 1.x just to confuse people even more. :-)

    8. Re:Sun and version by Anonymous Coward · · Score: 0

      Unless I am mistaken, there is a Solaris 7 (aka SunOS 2.7).

    9. Re:Sun and version by Surak · · Score: 2, Informative

      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. Note that Sun did eventually rename the older SunOS 4.x operating environment Solaris 1.x just to confuse people even more. :-)

      Thanks for clearing that up. :) You can clearly see why even I, who had more of a clue than the parent poster, was still confused. :)

    10. Re:Sun and version by sql*kitten · · Score: 0

      Just to pick nits, but the jump was from Solaris 2.6 to 7, not 8.

      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.

    11. Re:Sun and version by christophersaul · · Score: 2, Informative

      It's not version 1.0. There was a previous version which was around under the iPlanet and then Sun ONE brand and is used by various customers. It was version 3 then, to fit in with the fact it was an add-on to Portal Server 3.0. We're now at Portal Server 6.0, hence the numbering match.

      http://wwws.sun.com/software/products/portal_icp /h ome_portal_icp.html

    12. Re:Sun and version by Anonymous Coward · · Score: 0

      Hi,

      Still running Solaris 2.6.
      Not enough new stuff in 8???

      Perhaps you should attend to the Solaris 8
      Sysadmin Course.

      Why Solaris 8/9

      1. Logging file system.
      2. It's not END-OF-LIFED.
      3. Jumpstart with FLASH
      4. UFS-snapshots.
      5. Improved Memory Management.
      6. Improved DR technology.
      7. Improved Disksuite (metaset's,Soft partitions etc..., and working VERY well...)
      8 ...etc...

      Comparing sol 2.6 with 8 is like comparing windows
      3.1 and Win2000...

      Rgds, //DkY

    13. Re:Sun and version by hc000700070007 · · Score: 1

      First the abrupt jump from Solaris 2.6 to Solaris 8

      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

    14. Re:Sun and version by cpeterso · · Score: 1


      that's too bad because I always thought "Solaris Seven" (like "Oracle Eight") sounded like a cool name. :-)

  15. AIM Support by bjb · · Score: 1
    It would be nice if the server supported the latest AOL AIM standards. I was a daily user of AIM for years, but recently my company blocked access to it, and now we have an internal Jabber service. Fine, but there are a few people that I spoke with almost on a daily basis for years that I rarely talk to anymore (our conversations weren't large enough for phone, and not long or focused enough for email). We've got MSN messenger gateway service, but I'm not signing up for a Passport account to use it.

    I don't see why they couldn't do it, though. Wasn't there some link between Netscape, AOL and Sun? Should still be as far as I know.

    --
    Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
    1. Re:AIM Support by Anonymous Coward · · Score: 0

      AIM's protocol is unencrypted and requires touching the WAN to use. What company wants to send their sensative information out over the internet in plain text just to get it to the guy in the next cubicle?

      A jabber server can be run inside a firewall (just as the SUN IM can), can use 1024 bit encryption, and therefore greatly reduces the risk of having sensative information compromised.

    2. Re:AIM Support by Vengeful+weenie · · Score: 1
      This would be a great idea, and I know a few people working on similar projects.

      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.

    3. Re:AIM Support by idontneedanickname · · Score: 1
      Why don't you point your client at an AIM transport?

      Finding Gateways
      Using Gateways

    4. Re:AIM Support by Anonymous Coward · · Score: 0

      don't they have someting with Lotus Notes, namely Same time connect which is based upon AIM. My brother uses it you just have to set it to an other server, i.s.o the company's one.

  16. Market is wide open by LinuxXPHybrid · · Score: 5, Insightful

    > ... frankly it's too late for a new entry.

    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.

    1. Re:Market is wide open by pmz · · Score: 1

      There does not seem to be a wide margin in the IT industry in US, but there is China.

      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.

    2. Re:Market is wide open by Anonymous Coward · · Score: 0

      Sun doesn't have a competitive edge over Exchange or Domino, Exchange and Domino rule the corporate messaging market (combined market share of about 90%) because the products have matured over a proven series of releases and the features and functionality + ease of use far outweigh anything else out there...

      As for the 32bit vs 64bit argument, it just doesn't fly...there are very few if any environments where this is a limiting factor. Most Exchange and Domino servers are deployed on 4 way x86 (32bit) servers. The number of users per server supported on this type of server configuration numbers in the thousands, most corps get very anxious about putting all there users on a single server and simply scale out horizontally...horizontal scaling is almost always cheaper then vertical scaling.

    3. Re:Market is wide open by Anonymous Coward · · Score: 0

      Domino has been running on 64-bit UNIX for years. As pointed out -- few people run it that way, the ROI isn't there.

  17. Hey Moderators (OT) by Anonymous Coward · · Score: 0

    Would you mind checking the times on posts before marking them redundant?

  18. heh, erm by lingqi · · Score: 1, Insightful

    A lot of pals I yap with ARE from the office. And what's preventing the "all day yap" is because hanging out at eachothers cubes would attract volumous attention.

    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) you can speak in coded words. "new product announcement at the convention" = "movie that just got released" or something
    2) IT depts are stressed as they are - and they won't have that kind of time
    3) as for your boss, I am sure number 1 would work quite effectively - because if you work under a intelligent and capable boss, he would be smart enough to not have this whole nonsense in your dept anyhow.

    --

    My life in the land of the rising sun.

    1. Re:heh, erm by Sven+Tuerpe · · Score: 3, 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.

      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.

      --
      http://erichsieht.wordpress.com/category/english/
    2. Re:heh, erm by Anonymous Coward · · Score: 0


      Two machines is good, but I couldn't justify it to my boss. So I asked him for a dual-headed video card instead - he okay'd that. I then brought in my own 2nd monitor.

      Now that he sees the productivity gains, he's willing to allow me to retain my "old" machine and get an upgraded development workstation in the next budget cycle.

      Now that *I've* seen the productivity gains, I'll never go back to a single, single-headed machine.

  19. Re:Jabber by the+uNF+cola · · Score: 1

    But can you interface with their (sun) products, which you want?

    Jabber just wont fit.

    --

    --
    "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

  20. Real insightful, CowboyNeal by p3d0 · · Score: 4, Informative
    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.
    Yeah, it was the next logical step several years ago. IBM has been using the Sametime IM internally for as long as I have worked there.
    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    1. Re:Real insightful, CowboyNeal by Anonymous Coward · · Score: 0, Funny

      I checked out this loser's website - he doesn't work at IBM, he works at Pizza Hut!

    2. Re:Real insightful, CowboyNeal by Anonymous Coward · · Score: 0

      Yeah, it was the next logical step several years ago. IBM has been using the Sametime IM internally for as long as I have worked there.

      Ask someone who's been there longer than you about something called "VP Buddy". Some of us were disappointed when Sametime replaced VP Buddy(only usable inside the company).

    3. Re:Real insightful, CowboyNeal by sirtoby_tw · · Score: 1

      Even ICQ has had local service applications for _eons_..

      And Jabber exists since 1998, too.

      -towo

      --
      I think it would be a good idea. - Mahatma Gandhi, when asked what he thought of Western civilization
  21. Redhat by rf0 · · Score: 1

    One reason for Redhat going from 8 -> 9. Purely marketing. Normally people expect high numbers are better however it always become when someone releases version 11 of something. Is that v1.1 or v12? Lots of fun :)
    Rus

  22. This should be alright...as long.. by Quass · · Score: 3, Informative

    I work at a major corporation, and we use "Lotus Sametime" as our messenging client. At first I was put off by the lack of features (ie. timestamping, etc..) but it has interoperability with AIM, so I find it quite nice to use.

    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.

  23. Also Messaging for Customers, Partners and Remote by foniksonik · · Score: 2, Informative

    This isn't just for internal use... it works specifically with your firewall to provide secure authentication for Customers, Partners and Remote Employees around the world so you have a single sign on Messaging system for EVERYONE in your business.

    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.

    --
    A fool throws a stone into a well and a thousand sages can not remove it.
  24. feh by Anonymous Coward · · Score: 1, Insightful

    too little, too late .. and for this platform, useless at any rate. what outfit that you know of (that isn't stuck in the stone age) uses sun as a primary desktop platform? .. few to none. sun should just sell their assets off and run today while the running is better than tomorrow. hell, we're even switching to linux for everything, and we're definitely not a small shop. not that this necessarily precludes sun, but why couple free OS with pricey hardware that is no more stable than the cheaper stuff? .. expensive support, little if any third party products or competition - bleh. i loved sun back in the day, but a new day came, and we're with it.

  25. Future Sun Commercial by bahwi · · Score: 1, Funny

    Picture an employee at his desk. His AIM pop's up:

    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!

  26. back in my day.. by Anonymous Coward · · Score: 0

    we didn't need any fancy messaging clients:

    $ mesg y ; man write
    $ man talk

    kplzthxgoal.

  27. BTW, UFS logging was available in Sol8 by mister_jpeg · · Score: 1

    with the logging option in /etc/vfstab.

    --
    -jpeg
    1. Re:BTW, UFS logging was available in Sol8 by AKnightCowboy · · Score: 1

      Not to nitpick, but UFS logging was introduced in Solaris 7. I remember thinking, "finally I don't need to wait a half hour for my damn drive to fsck anymore" after a power outage or a crash. :-)

  28. Thank goodness. by FreeLinux · · Score: 1, Funny

    We were really lacking in the instant messaging server department. No if they would only come out with an MP3 player, they'd take over the world.

    1. Re:Thank goodness. by Penguuu · · Score: 1

      And other good killer-application would be peer-to-peer filesharing software! That would be something completely new, and media-corporations would love you, because your software would give free advertising to their artists!

      --
      The problem in the world today is communication. Too much communication - Homer Simpson
  29. this is a lie by Mohammed+Al-Sahaf · · Score: 1, Funny

    The website does not exist. It has been destroyed by the grace of Allah and the infidels who created it were chased away to their deaths by the mighty Iraqi Army.

    --
    Former Iraqi Information Minister Mohammed Saeed al-Sahaf
    1. Re:this is a lie by Anonymous Coward · · Score: 0

      Rivers! Rivers of ASCII, I tell you, as their pages were smashed by the Republican Guards.
      We made Perl out of those mercenaries!

  30. zwrite by cacheMan · · Score: 1

    I've been using IM on a sun network for years.

  31. ZeroConf is a better solution by Anonymous Coward · · Score: 0

    Why a server in the first place? This is an ideal situation for ZeroConf. It will automically constrain to the corporate LAN or workgroup (depending on how IT constrains the network). And no server is required at all. Try iChat for an example of how this works. You just launch the messaging app and everyone is automatically detected.

  32. I can't wait till... by mrwonka · · Score: 0

    i get to bling use an instant bling messenger at bling work.

    Honestly, I think email is enough of a distraction at work. I can't count the number of times that i've been coding away.. and an email pops up... which gets me out of the groove.

  33. So I read a bunch of the replies.. wtf? by sporty · · Score: 2, Interesting

    Did you people bother read the article? Jabber doesn't integrate with sun's suite. If they foudn the technology usable, the may have used it.

    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.

    --

    -
    ping -f 255.255.255.255 # if only

  34. Do you mean by einhverfr · · Score: 1

    The commercial jabber client at jabber.com?

    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.

    --

    LedgerSMB: Open source Accounting/ERP
  35. Wrong by Andy+Dodd · · Score: 3, Informative

    As far as RH going straight from 8->9

    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.

    --
    retrorocket.o not found, launch anyway?
  36. Domino? Please by tmasssey · · Score: 4, Interesting
    I cringe every time I hear something like this being compared with Domino. Yes, Domino does e-mail. Yes, Domino does calendaring. But Domino is so much, much more.

    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.

  37. Sun One = chillisoft by Anonymous Coward · · Score: 0

    If people remember, chillisoft made it possible to do asp on *unix based systems. It was recently takes into Sun as Sun One.

    If anyone's played with Sun before, this will most likely end up in another propietary mess. You have to buy a sun machine, instead of using your own servers, get their licenses for the OS, software, and seats and other crap if you want it to tie in with the rest of their Sun suite.

    Plus, you can't put it in yourself, so you have to pay for their consulting fees. To which, the consultants from Sun know enough to start the engine and the basic setup.

    And at the end of Sun's quarter, you'll get phone calls and emails if you're happy with the services and be asked if you want to upgrade. It's a never ending cycle, how do I know? I just freaking know...

  38. Re:Jabber by wirefarm · · Score: 1

    If Sun is using closed protocols that can only interface with other Sun programs, what the hell good are they? The Open Source Community might just adopt their functionality and leave them in the cold. Again.

    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.

    --
    -- My Weblog.
  39. lemme guess by _ph1ux_ · · Score: 1

    its called WALL!!??

  40. old news... by Anonymous Coward · · Score: 0

    Instant Messaging Planet (http://www.instantmessagingplanet) covered this months ago when the Sun product manager unveiled the product and spoke about it at the Enterprise IM conference in Boston.

  41. FINALLY! by Big+Nothing · · Score: 2, Funny

    Another IM service is just what I've been missing!

    --
    SIG: TAKE OFF EVERY 'CAPTAIN'!!
  42. trillian + modified IRC= STANDARDIZED IM by romerom · · Score: 1

    why can't some IRC developers come up with an addon that would allow for voice chat as well as viewing of webcams? Then if a company like trillian or whoever would write an IM client that uses those features of the IRC server.. it would seriously kick ass.. but to regular IRC users.. it would look just like normal IRC.. ya get me?

    --
    http://www.awwsheezy.com
    1. Re:trillian + modified IRC= STANDARDIZED IM by syberdave · · Score: 1

      That's not hard... just add a new feature that works like dcc chat.

      One client requests, gives a ip and a port, and the other client connects and can send data.

  43. there's gaim with cross-platform rsa encryption! by accessdeniednsp · · Score: 1

    A few shameless plugs, yes, but the facts remain. Gaim is available for a plethora of platforms. Of those platforms, the Gaim-Encryption plugin works on 4 of them: Solaris (Sparc), Linux (x86), Win32, and Familiar Linux on the iPAQ (arm).

    The Gaim-Encryption plugin uses OpenSSL with RSA keys, auto key exchange, etc. Really really good stuff. And best I can tell, gaim is now the ONLY IM client with cross-platform encryption. The encrypt plugin lets you talk crypto across ANY of the IM platforms gaim supports, which is not a short list: AIM, MSN, IRC, Jabber, Yahoo!, ICQ, Napster(?), Zephyr, and Gadu-Gadu.

    The Gaim-Encryption maintainer provides pre-built packages and installers for several distros and Win32. So you can get it all in one spot.

    Seriously, "It Works. Well(tm)".

  44. Jabber is far more than an IM service. by Anonymous Coward · · Score: 0

    Jabber is a generic distributed message-passing system. Just because there is an IM system built on top of it, people think that that is all that it can do. Do some research! Learn about something before you demean it!

  45. Re:Jabber by sporty · · Score: 0

    Open standards aren't a panacea. I love saying "isn't a panacea".

    Opensource is good and all. Open standards are great and all as well. But you can't judge a product on its openness. After all, is the sorenson codec or OS X (both apple) bad? How about trillian? Great piece of software... and it's closed.

    --

    -
    ping -f 255.255.255.255 # if only

  46. Jabber is *not* an IM service... by idontneedanickname · · Score: 1
    I quote from above:

    "Jabber is *not* an instant messaging protocol. It just happens to be useful for instant messaging ;-) Jabber is a protocol for streaming XML."

  47. Novell also released an enterprise IM by KKBaSS · · Score: 1

    Novell has also recently come out with an enterprise secure IM product, it integrates into edir directly. Free for groupwise 6.5 owners. More information can be found here -
    http://www.novell.com/documentation/lg/nm1/readmee n_web/readmeen_web.html
    http://www.serverwatch.com/news/article.php/10824_ 1555761_2
    http://www.instantmessagingplanet.com/enterprise/a rticle.php/1548151
    http://www.appdeploy.com/packages/detail.asp?id=86

  48. Whoopity do by Anonymous Coward · · Score: 1, Funny

    ...And it will be called YAPPOSIMS
    or Yet Another Proprietary Piece of Sh*t Instant Messaging Standard

  49. Re:Sun and version (OS/Kernel) by Tpenta · · Score: 1

    I note that someone has addressed the 6.0 issue with the IM. I can do a little with regard to the clarification of 5.8/8 etc.

    First off, Solaris went from Solaris 2.6 to Solaris 7. Note that this number is a representation of the Operating Environment.

    Now, when you start talking about 5.8, you are talking about the kernel.

    5.7 is the kernel that goes with the Solaris 7 OE
    5.8 is the kernel that goes with the Solaris 8 OE
    5.9 is the .... you get the picture.

    So it's not a case of Solaris 8 reporting itself internally as 5.8. The uname -a output is giving you the kernel version.

    It's no different from RedHat X using Linux version Y.

  50. Does the icq transport work now? by Anonymous Coward · · Score: 0
    A year ago I stopped using jabber because the icq transport was very unstable. What is the present status of the icq transport. Is it stable enough to be useful?

    Does this require me to run my own Jabber server?

    Does this require me to code my own Jabber server?

  51. XP is old fashioned ... by Anonymous Coward · · Score: 0

    .net suffix is dead ... so, they should call it 2003 instead :o)