Under The Hood Of I2p, The Tor Alternative That Reloaded Silk Road | Ars Technica

Solace Enables IBM-based Application Infrastructure to Meet Demands of Next-Generation Applications – Yahoo Finance

Instead, the network directory of I2P is netDb, a distributed database that is replicated across the network. The NetDb is a distributed hash table similar to Kademlia, a peer-to-peer network developed by Petar Maymounkov and David Mazieres that was also used by LimeWire to improve the Gnutella file-sharing protocol. The netDb network database contains information on active routers (peers on the network available for routing traffic) and endpoints, such as “eepsites” and exit points to the public Internet, including their Internet location, the network port number they listen on, and their public encryption keys. An I2P router can be configured to opt in as part of the distributed storage system, called the “Floodstore”; since the database is constantly verified and updated each time a connection is made, there’s no inherent trust of the database involved in routing traffic. While this makes I2P useful for things like anonymized BitTorrent streams and the like, it does not have the scale or the level of additional protections that the Tor network provides. There are no tools to help get around state-imposed firewalls, for example, like Tor’s pluggable transports and bridges. But being small has made I2P less of a target for denial-of-service attacks and state blocking so far.
For the original version including any supplementary images or video, visit http://arstechnica.com/information-technology/2015/01/under-the-hood-of-i2p-the-tor-alternative-that-reloaded-silk-road/

Here are some of the ways Solace integrates with specific IBM technologies: Solace message routers support native integration with DataPower appliances so customers used to the benefits hardware acceleration brings to their ESB, B2B and enterprise integration projects can now unlock even better performance, predictability and ease of use with an end-to-end appliance-based infrastructure. Solace integrates with IBM Integration Bus and IBM WebSphere Application Server via JMS and JCA in the container layer so companies can connect new applications to Solace message routers without any Solace-specific code. In fact, they can switch existing applications from WebSphere MQ-based messaging to Solace without changing any code. Solace message routers can make CICS and IMS applications on the mainframe accessible to modern distributed applications by integrating with them via IBM DataPower appliances or IBM Integration Bus, bridging to WebSphere MQ on the mainframe, or via WebSphere Liberty z/OS Connect. Solace can be integrated and coexist with WebSphere MQ messaging software through the use of a simple “bridge” or via the other IBM technologies described above so companies can rely on both technologies simultaneously, either as a hybrid environment or during migration. Solace’s native integration with IBM will be available in the first quarter of 2015.
For the original version including any supplementary images or video, visit http://finance.yahoo.com/news/solace-enables-ibm-based-application-140127649.html