There is now an official 1.0 release of Jabber-Net, with binaries and
source available for download at:
http://code.google.com/p/jabber-net/downloads
New features that you might not know about:
- DNS SRV
- Compression
- Kerberos/GSSAPI
- RosterManager
- PresenceManager
- ConferenceManager
- PubSubManager
- CapsManager
- DiscoManager
- XmppDebugger
Thanks to everyone that has reported bugs and requested features over
the years.
<commercial>
You can still use Jabber-Net under the GPL or JOSL, but if you would
like to buy commercial support, my employer, Jabber Inc., is offering
a fully-supported version of the library that adds XCP-specific
features and more documentation. Contact me off-list if you would
like more information.
</commercial>
--
Joe Hildebrand
I subscribed to this forum because I'm interested in using Jabber as a file
transport between disconnected parties. Now that v1.0 is available I'd
like to renew my interest and see if I can make this happen.
However, I'm confused about where I can find info to get started. The
code.google.com site doesn't point to docs except for a couple helpful but
sparse wiki pages. So I googled for "jabber.net" and "jabber-net". I
found the cursive.net page which referred back to google. I also found the
SourceForge page. That says the project moved to jabberstudio, which has
been shutdown and leads back to home pages completely unrelated to Jabber.
The Open-Source Projects link at jabber.org leads to that same dead-end
jabberstudio page. The license.txt in the project itself still references
the now dead JOSL.
I found this page buried in a list of google results:
http://new.jabber.org/node/150
It teases the visitor with a list of docs including an API for jabber-net,
but alas none of these links actually lead to jabber-net docs.
I've never witnessed this sort of _community_ incompetence, with dead links
everywhere and no one in this wide world of FLOSS taking initiative to
create a lousy web page at a stable website with a few links pointing to
it.
Please create a home page for this project somewhere so that we can spend
some time online and read about all of these wonderful features that you've
added. If we have no idea how to use it then your effort is wasted.
BTW, due to your mention of your employer, I visited jabber.com and was
impressed by the diversity of offerings - congrats.
Thanks.
I've updated the link at SourceForge, which I had overlooked. If you
can send me the URLs of the other pages you've found that point to
invalid places, I'll do my best to get them changed.
As to documentation, if you download a compiled version of the
project, particularly the 2005 version, you should find a .chm with
relatively complete API documentation. As well, I've uploaded
the .chm to the files section of Google Code that you can download
directly:
http://jabber-net.googlecode.com/files/jabber-net.chm
If you find a class that you can't figure out how to use, please post
here, and we'll try to answer your question, and I'll try to make the
documentation better.
--
Joe Hildebrand
You need to get out more. And I'm only partly joking. :) Seriously, an
Open Source project with a useful and current web site is the exception,
it certainly [absolutely] is *not* the norm. I've been administering a
largish network on primarily Open Source software for just shy of 15
years [man, I'm getting old sooo fast] and there is nothing exceptional
about the chaos surrounding jabber-net.
> Please create a home page for this project somewhere so that we can spend
> some time online and read about all of these wonderful features that you've
> added. If we have no idea how to use it then your effort is wasted.
> BTW, due to your mention of your employer, I visited jabber.com and was
> impressed by the diversity of offerings - congrats.
I've personally had experience developing on projects that have moved;
and it can be as frustrating from the projects side as it is from the
user's side. Dead pages and derelict links, etc... often times one
looses the access required to go back and remove/fix them. It is like
the cholesterol of the Internet.
--
Adam Tauno Williams, Network & Systems Administrator
Consultant - http://www.whitemiceconsulting.com
Developer - http://www.opengroupware.org
The following text comes from:
http://support.microsoft.com/kb/232077/
======
...However, Internet Explorer contains a predefined, hard-coded list of
file extensions that it inherently distrusts. These extensions correspond
to generic executables and other kinds of files that have the capability to
harm the user's machine without the proper security safeguards. The File
Download dialog box cannot be prevented for any files of these types. The
Always ask before opening this type of file option will be grayed out on
the dialog box and you will not be able to select it. Following is the list
of the file extensions for these file types.
======
(chm and msi are both on the list)
HTH and Sorry... :)