From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Monday November 13, 19100 @ 4:37
Author: burton
CVSWEB Options: -------------------
Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi
View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes
-----------------------------------
Update of /usr/local/cvsroot/openprivacy/htdocs/notes
In directory openprivacy.org:/tmp/cvs-serv16408
Modified Files:
primary-agent-protocol.txt
Log Message:
should meet all requirements... that fen and I talked about... I think
*****************************************************************
File: openprivacy/htdocs/notes/primary-agent-protocol.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/primary-agent-protocol.txt?annotate=1.3
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/primary-agent-protocol.txt?rev=1.3&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/primary-agent-protocol.txt.diff?r1=1.3&r2=1.2
-----------------------------------
Index: openprivacy/htdocs/notes/primary-agent-protocol.txt
diff -u openprivacy/htdocs/notes/primary-agent-protocol.txt:1.2 openprivacy/htdocs/notes/primary-agent-protocol.txt:1.3
--- openprivacy/htdocs/notes/primary-agent-protocol.txt:1.2 Mon Nov 13 03:34:22 2000
+++ openprivacy/htdocs/notes/primary-agent-protocol.txt Mon Nov 13 04:37:13 2000
@@ -1,6 +1,6 @@
********************************************************************************
-$Id: primary-agent-protocol.txt,v 1.2 2000/11/13 11:34:22 burton Exp $
+$Id: primary-agent-protocol.txt,v 1.3 2000/11/13 12:37:13 burton Exp $
Notes for a Primary Agent Protocol.
********************************************************************************
@@ -19,22 +19,43 @@
- Allows a simplification of the system.
-
Requirements:
- Need a way to lookup a set of capabilities. Core capabilities should be
integrated into the client so that they are already known about (storage,
secondary agent lookup (for reputation based capability offloading),
reputation lookup, additional capability lookup)
+
+ - capability lookup should be based on......
- - capability lookup should be based on
- reputation
- price (need an abstraction of this)
- - speed (bandwidth? CPU?) because just because a given agent has a high
+ - speed (bandwidth? CPU? current load?) because just because a given agent has a high
reputation doesn't mean that you can use it from a low bandwidth
- location.
+ location.
- - At this point the raw data would
+ - At this point the raw data would be given to the client (reputation, price,
+ etc) and it would be up to client 'rules' to make the decision on which
+ agent to use. Part of this communication is the URI used to denote the
+ capability. It is up to the client to support communication to the
+ agent/capability.
-- Need a method to expose
+ - Required capabilities?
+ - When a primary agent ships... it is probably required to have support for
+ some misc capabilities:
+
+ - profile storage
+ - additional capability lookup
+ - secondary agent lookup (so that the user can get additional functionality)
+
+Protocol:
+
+- It is probably a requirement that each agent speaks HTTP (or at least on that
+ port). If the client is using HTTP 1.1 we can encode an XML payload and then
+ get a response back (this works over firewalls).
+
+ - POST at / an XML Payload
+ - GET an HTTP error code back on success/failure.
+ - RECEIVE an XML document back with contains additional information.
+
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST