ietf-openproxy
[Top] [All Lists]

RE: Proxylet API: IDL version

2001-11-06 12:15:35

Andrew, 

I was going to post your API document on the http://www.ietf-opes.org/ web
site when browsing through Thundercrack site
(http://www.thundercrack.com/randd.htm) I've found the statement copied
below.

Are the Thundercrack APIs proposed to the IETF falling under this patent
statement ?
Thank you for the clarification.
Christian



Please note that the Thundercrack Server Software is now Patent Pending in
the US.
Thundercrack is participating in the standardisation of edge applications.

Thundercrack PIPE is our first generation Edge Processing Engine. PIPE
engages proxylets at the delivery edge on behalf of content owning sites.
These proxylets are authorised by the origin server to carry out arbitrary
data modifications to request and response messages going to the origin
server. This enables Thundercracks suite of DRM proxylets to deliver the
correct content to the paying customer. The dynamic deployment of proxylets
to the edge servers allows the available processing power to the origin
server to be stepped up whenever demand dictates, and reduced when the
demand subsides. The content delivery networks, and web hosting companies
will be able to deliver burstable processing power to their customers web
sites. So a web site may reduce the number of servers within their site
cluster and lease in on demand processing from the delivery service to
fulfill their digital rights managed delivery.

For more information on the work of the Internet Engineering Task Force
working group please click here: www.ietf-opes.org


-----Original Message-----
From: Andrew Walker [mailto:andrew(_dot_)walker(_at_)thundercrack(_dot_)com]
Sent: Monday, November 05, 2001 5:45 AM
To: ietf-openproxy(_at_)imc(_dot_)org
Subject: Proxylet API: IDL version



All,

I have rewritten the proxylet API as IDL, its still largely 
the same as 
before, but it should be easily transferable to other languages. 
Details may be found here. For explanations of the individual 
methods, 
read the inlined comments within the idl and the previous 
draft document.

http://www.thundercrack.com/drafts/proxylet_api_0.2_idl.tar.gz

There are subtle differences between the pure java api and this one.
 o Exceptions dont exactly match the previous pure java 
objects. Though they 
are simillar.
 o Where methods were overloaded the method names now reflect 
the passed 
parameters. Idl doesnt support method overloading.

There is a set of uml class diagrams in the archive for reference.

As always, comments are appreciated.

-- 
Regards,

Andrew Walker
Thundercrack Ltd.
17 Rathbone Street
London, W1T 1ND
UK
 
Phone:  +44 020 7631 1000
EMail:   andrew(_dot_)walker(_at_)thundercrack(_dot_)com
URI:     http://www.thundercrack.com


<Prev in Thread] Current Thread [Next in Thread>