[
Lists Home |
Date Index |
Thread Index
]
- From: "Gregory M. Messner" <gmessner@messners.com>
- To: xml-dev@ic.ac.uk
- Date: Fri, 25 Sep 1998 07:43:58 -0700
I have 2 questions/problems:
1) A DTD describes a document which contains content specified by a URL, a
local file name, or inline. Documents created using this DTD are assembled
and transported across a network. How do you include the content? The 2
ways we have discussed are:
* Inline using Base64 encoding in a CDATA section
* Wrap the document in a multipart/related MIME message
and include the content as attachments
I am leaning towards multipart/related, but would like to know of others
experience in this area.
2) We desire to provide an API on the client side which exposes a simple
mechanism for creating and modifying objects. These objects are serialized
using XML and then transported to a server for further processing. The
server then responds with another XML document that we then de-serialize
into an object and present it to the API user. Here are some basic
requirements:
* Support for both Java and C++
* API must be similar for both Java and C++
* Object members are accessed via get/set methods
* Adhere to JavaBean method naming patterns
We are thinking of developing an application which takes a DTD and then
generates Java and/or C++ code for each object. We would use a XML helper
file to give more control over the generation process. Are we out in left
field here? What are some of the other ways to do this? What are you
experiences doing something like this?
Gregory M. Messner
gmessner@vsi.com
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|