|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (5)
View Page History... |
| Fudge, however, *is _not_ a Message Oriented Middleware platform or standard.* While Fudge works well in MOM environments, it really focuses more on what goes in the body of the messages you send. Fudge works great with HTTP, JMS, and AMQP as the underlying network transport. |
| h2. Project Status While Fudge is still in early days, it's presently being used in production by several applications. * A binary [Encoding Specification] that defines how Fudge data is to be encoded; * A [Java|Java Development] reference implementation; * A [C#/.Net|CSharp Development] reference implementation; * A [C|C Development] reference implementation; and * A [Google Protocol Buffers|Fudge Proto] compatibility library. You can track the precise status in our [Releases] page. |
| h2. Why Should I Use Fudge? |
... |
| h2. Project Details * [License] : Fudge libraries are offered under the APLv2. |
| * [Copyright] : Currently, all copyright to Fudge libraries is held by [OpenGamma|http://www.opengamma.com/] Inc. |
| * [Sponsorship] : The Fudge Messaging project is sponsored by [OpenGamma|http://www.opengamma.com/]. |
| |
| h2. Project Status Fudge is very much an early-stage project. Presently we have: * A binary [Encoding Specification] that defines how Fudge data is to be encoded; * A [Java|Java Development] reference implementation; and * A [C#/.Net|CSharp Development] reference implementation. We're early enough that we don't even have pre-made downloadable packages yet, though that's forthcoming. |
| h2. Getting Started The easiest way to get started is to look at the [Encoding Specification], or the [Types] taxonomy, or the [Source Code]. Then, join the [Mailing List]. |
... |
| h6. Navigate space |
| {pagetreesearch} |
| {pagetree} {column} |
... |