ICE Protocol Reference Java Code / News: Recent posts

ICEcubes 0.5 source is now available as a release package for your development . Note that this is a very early release of the source code for the reference implementation of ICE 1.1 and ICE 1.2. This release has the core framework complete and the basic managers are now running ( policy, log, scheduler, ask, kernel , etc.) but this is useful only for developers.

The latest updates to icecubes is now in the repository.
We are now using the August release of Xerces parser;
XMLdisassembly is now very close to final form (bugs excepted). The preliminary interface to TomCat is now in the system. Several of payloadAssembly routines have been written. The new collection manager is in.
We are now working on the StorageManager and the dispatching system. Oh, the PolicyManager is nearly complete. You can define policies in configure.xml and
the PolicyManager will read them in and make them available.

Well, after some major investigation, it turns out that I didn't have the correct version of SSH installed. Once it was installed, the files imported right up.

So, now we'll just have to keep it up to date.

Thanks for your assistance in getting this solved.

IceCubes is an Open Source Java Implementation of the Information & Content Exchange (ICE) Protocol Version 1.1. It is being developed and led by the ICE authoring group, the people who wrote the ICE specifications. The ICE protocol standard and associated information is available from

http://www.icestandard.org

ICE is a session level request/response protocol that can use any reliable transport level protocol with HTTP being the most popular transport . ICE's messages are XML documents. ICE is designed to solve the content syndication problem. That is, it solves the problem of a content provider reliably delivering periodically updated content to many users . ICE provides a protocol to enter into a content syndication relationship and have that relationship managed and automated. In the prototypical syndication relationship, a content provider, called a syndicator, creates multiple collections of content and a catalog of offers for delivering that content. Upon request, a syndicator sends the catalog of offers to a prospective user, called a subscriber. A syndicator accepts messages containing offers from subscribers. A syndicator and subscriber arrive at a mutually agreeable set of parameters described in an offer using parameter negotiation and thereby establish a subscription. A subscription is an agreement between a syndicator and a subscriber for the delivery of selected content during a span of time according to a delivery policy and within a set of business terms. The parameters that are negotiated consist of operational parameters and business term parameters. Operational parameters control the characteristics of delivery such as push or pull delivery, frequency of update, delivery dates, time between deliveries and unit quantities to be delivered; and thereby define the delivery policy. Business term parameters are any set of syndicator - subscriber defined parameters that are useful to the syndication relationship. These might consist of the parameters for special services provided by the syndicator or subscriber such as additional content protection, summarization or performance. Parameter negotiation is not restricted to operational parameters. The mechanism can be used to negotiate any set of expressable parameters at any time during a subscription.... read more