[Bio] / FigCommon / SeedRegistry Repository:
ViewVC logotype

View of /FigCommon/SeedRegistry

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (download) (annotate)
Fri Dec 19 22:57:48 2003 UTC (15 years, 10 months ago) by olson
Branch: MAIN
CVS Tags: mgrast_dev_08112011, rast_rel_2009_05_18, mgrast_dev_08022011, rast_rel_2014_0912, rast_rel_2008_06_18, rast_rel_2008_06_16, mgrast_dev_05262011, merge-trunktag-bobdev_news-2, rast_rel_2008_12_18, mgrast_dev_04082011, rast_rel_2008_07_21, rast_rel_2010_0928, rast_2008_0924, mgrast_version_3_2, mgrast_dev_12152011, Root-bobdev_news, rast_rel_2008_04_23, merge-bobdev_news-1, help, mgrast_dev_06072011, rast_rel_2008_09_30, rast_rel_2009_0925, rast_rel_2010_0526, rast_rel_2014_0729, merge-trunktag-bobdev_news-1, mgrast_dev_02212011, rast_rel_2010_1206, caBIG-05Apr06-00, mgrast_release_3_0, mgrast_dev_03252011, rast_rel_2010_0118, mgrast_rel_2008_0924, mgrast_rel_2008_1110_v2, rast_rel_2009_02_05, rast_rel_2011_0119, merge-bodev_news-3, lwc, mgrast_rel_2008_0625, mgrast_release_3_0_4, mgrast_release_3_0_2, mgrast_release_3_0_3, mgrast_release_3_0_1, mgrast_dev_03312011, caBIG-00-00-00, mgrast_release_3_1_2, mgrast_release_3_1_1, mgrast_release_3_1_0, merge-bobdev_news-2, mgrast_dev_04132011, rast_rel_2008_10_09, mgrast_dev_04012011, rast_release_2008_09_29, mgrast_rel_2008_0806, mgrast_rel_2008_0923, mgrast_rel_2008_0919, rast_rel_2009_07_09, rast_rel_2010_0827, mgrast_rel_2008_1110, myrast_33, rast_rel_2011_0928, rast_rel_2008_09_29, mgrast_rel_2008_0917, rast_rel_2008_10_29, mgrast_dev_04052011, mgrast_dev_02222011, caBIG-13Feb06-00, rast_rel_2009_03_26, mgrast_dev_10262011, rast_rel_2008_11_24, rast_rel_2008_08_07, merge-trunktag-bodev_news-3, HEAD
Branch point for: Branch-bobdev_news
new stuff, so it doesn't get lost.

SEED Instance Registry
========================
Robert Olson <olson@mcs.anl.gov>
Dec 2003

The SEED instance registry is a network facility that allows users of
SEED instances to register these instances and  to look up the list of
registered instances for the purpose of performing peer-to-peer
updates. 

The Registration Process
------------------------

The following information is maintained for each registered seed:

*Instance ID*. A unique identifier for the SEED instance.

*Name*. A human-readable name for the SEED instance, provided by the
SEED user registering the instance.

*URL*. The URL to the SEED instance.

*Comment*. A free-text comment about the seed instance.

Registration API
~~~~~~~~~~~~~~~~

We define a simple HTTP GET/POST API for manipulating the registry.

The high-level functions provided are as follows.

- Register. Register a new SEED instance. This registration returns a
  cookie that can be used to later change or delete the registration.

- Unregister. Remove a SEED registration.

- Retrieve. Return a list of SEED instances (in machine-parsable format).

- View. Return a human-readable HTML form of the list of SEED
  instances.

Register
^^^^^^^^

This is an HTTP POST with the arguments encoded in standard
application/x-www-form-urlencoded format. The following values are
expected to be passed:

*id*. SEED instance identifier.
*name*. SEED instance name.
*url*. SEED instance URL.
*comment*. Comment.

The return is also in application/x-www-form-urlencoded format, with
the following values:

*status*. Status code.
*token*. A unique token used to change the registration entry in the
*future. 


MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3