Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

RabbitMQ 1.3.0 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News RabbitMQ 1.3.0 (Default branch)
# 1  
Old 04-02-2008
RabbitMQ 1.3.0 (Default branch)
RabbitMQ is an implementation of AMQP, the emerging standard for high performance enterprise messaging. The RabbitMQ server is based on a proven platform, Erlang/OTP, offering exceptionally high reliability, availability, and scalability. It delivers good throughput and latency performance that is predictable and consistent. The code base is compact and easily maintainable, facilitating rapid customization and hot deployment. The RabbitMQ distribution also includes a Java client that interoperates with any compliant AMQP server. License: Mozilla Public License (MPL) Changes:
This release fixes a number of race conditions and other bugs, improves performance, and has better error reporting.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

OpenMQ, ActiveMQ or RabbitMQ

I am trying to form a proper proposal for my project however I do not know exactly what I can do. I was thinking whether I could work on a client side library which enables that client to connect to a known broker such as OpenMQ or ActiveMQ. Have you got any ideas which may be the best client,... (0 Replies)
Discussion started by: tyron
0 Replies
Login or Register to Ask a Question

LEARN ABOUT OPENDARWIN

opieserv

OPIEKEY(1)						      General Commands Manual							OPIEKEY(1)

NAME

       opieserv - Example OPIE-based OTP server

SYNOPSIS

       opieserv
       [ principal ]

DESCRIPTION

       opieserv  takes an OTP principal (e.g., a user name) from either the command line or standard input and returns a current OTP challenge for
       that principal. It then reads an OTP response to that challenge from standard input and displays a message and returns a value to  indicate
       either success (exit value = 0) or failure (exit value = 1). It is intended as an example for programmers of how a simple OTP server can be
       built.

EXAMPLE

       wintermute$ opieserv kebe
       otp-md5 495 wi01309
       Response:
       User verified.
       wintermute$

SEE ALSO

       opiegen(1), opiekey(1), opie(4), opiepasswd(1), opieinfo(1), opiesu(1), opielogin(1), opieftpd(8), opiekeys(5), opieaccess(5)

AUTHOR

       The opieserv1) program was created by Craig Metz for OPIE 2.2.

       Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan
       McDonald, and Craig Metz.

       S/Key is a trademark of Bell Communications Research (Bellcore).

CONTACT

       OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join, send an email request to:

       skey-users-request@thumper.bellcore.com

7th Edition							 February 20, 1996							OPIEKEY(1)