Archive for the 'Openfire Server' Category
Like many other people I tend to use instant messaging on a lot of different workstations: at home, at work, on my notebook and sometimes from abroad using the Jeti Applet. With the current generation of mobile phones, even these devices offer decent support for IM.
This all works very well with one major drawback: the […]
You may remember me asking for everyone’s help a few months back to vote for Openfire. We’re entered in the Enterprise Open Source Reader’s Choice Award in the “Best Open Source Product” category. The deadline for voting is May 31, which is just one week away. If you haven’t already voted, please visit the site […]
I’ve recently run into a number of innovative sites and products that use Openfire.
IMified provides tools like task management, reminders and todo’s through IM bots on AIM, MSN, and XMPP/GTalk. They’ve just released an API that will make it easy to write bots that work across all major IM networks. Openfire powers their XMPP back-end.
Mosoto […]
The engineering team at Jive Software is growing fast (btw, we’re hiring!). I thought it might be interesting to talk about some of the engineering process changes we’re making to cope with that growth, especially since they directly affect product releases. First, a bit of history. We’ve always had a fairly agile development process — […]
As the lead developer of the web-based version of a voice trading system used world-wide by some of the largest financial organizations, I have learned one or two things about web-based VoIP applications. When we designed our trading application, web-based VoIP was not ready for the 99% reliability and quality demanded for financial transactions. We […]
As many of you may have noticed. the IM Gateway plugin version 1.0 was released alongside Wildfire 3.2.3. (sorry guys, I can’t call it Openfire until the official release is 3.3.0 ) The release was quite a step for me as I’ve never actually released a 1.0 of anything! Typically […]
Today we re-launched Wildfire using the Openfire name. Along with the name change, we also have a great new logo. I wanted to provide some details about how the name change is being implemented to decrease confusion.
First, you’ll notice that all website content has been updated to Openfire. There may be a few […]
I’m pleased to announce that we’ve chosen a new name for the Wildfire server: Openfire. There’s several things I really like about the new name:
We preserve the fire theme, which makes for an easier transitition. In fact, we’re working on some snazzy updated logo ideas right now.
The new name better communicates two of the strongest […]
Smack uses an XML Pull Parser (XPP) to parse XMPP stanzas and build custom Packet objects. Wildfire represents XMPP stanzas as DOM objects wrapped by Packet objects. Each approach has its own pros and cons. Moreover, in Wildfire we can use different parsers to generate DOM objects.
For Wildfire 3.2 we needed to change the way […]
Thanks to everyone for the feedback on our need to move to a new name
for Wildfire. We are still working on a new name to take the
place of Wildfire. Also, based on the blog posts we received, we
realized that we should provide more clarification on how the trademark
issue arose, and our need to move to […]
