[usmt dev] usmt
Wed, 14 Feb 2001 17:04:42 -0500 (EST)
I will explain the justification for each, assuming that they can encode
the same information in the same structure (if a demonstration is need i
will give examples)
XML, is designed for transport of ordered inforamtion like this, it
provides a tree structure of records. each record may contain sub records.
each record is not forced to be/contain any type.
its format is portable.
MIME multipart, is designed to transport mulitple records inside of a
single record, like XML it can contain subrecords. MOST MUAs have
facilities to parse the MIME multipart structure.
the format is know to MUAs
- Jason Pyeron Pyerotechnics Development -
- Projects Manager Suite 101/2937 St Paul St -
- 410 467 2266 Baltimore, Maryland 21218 -
On Wed, 14 Feb 2001, Mike Schiraldi wrote:
> I've been trying for weeks to come up with a protocol for USMT that's
> simpler than XML but still does everything we need. After going back to
> the drawing board many times (and realizing at one point that i'd
> reinvented LISP), i'm about ready to give up and use XML. I was hoping
> someone might have a suggestion.
> Consider the following two commands. What kind of protocol could handle
> both of them in a similar manner?
> "Take these records and put them in your database: 'One Record: Addr =
> firstname.lastname@example.org, Type = x509-cert, Data = asdfgdfgdfsg ... Another Record:
> Addr = email@example.com, Type = pgp-public-key, Data = bkcjlkjgldskjdfg'."
> "Look up records using LDAP and store them in your database. Give these
> parameters to the LDAP engine: RootURL = ldap://ldap.openldap.org, BaseDN
> = 'dc=foobar, dc=com'"