|
Check-in Number:
|
3276 | |
| Date: |
2003-Feb-17 13:52:59 (local)
2003-Feb-17 12:52:59 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
better abstract |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-web/pkg/lib/xds/index.wml 1.5 -> 1.6
--- index.wml 2003/02/17 12:42:15 1.5
+++ index.wml 2003/02/17 12:52:59 1.6
@@ -7,19 +7,14 @@
<h2>Abstract</h2>
-The purpose of OSSP xds is to encode data in a way that allows this
-data to be exchanged between different computer systems. Assume you
-would want to transfer the value 0x1234 from host A to host B. Then you
-would encode it using B<OSSP xds>, transfer the encoded data over the
-network, and decode the value again at the other end. Every program that
-follows this process will read the correct value no matter what native
-representation is uses internally.
-
-<p>
-OSSP xds consists of three components: The generic encoding and decoding
-framework, a set of engines to encode and decode values in a certain format,
-and a run-time context, which is used to manage buffers, registered engines,
-etc.
+The OSSP xds library is generic and extensible encoding and decoding
+framework for the serialization of arbitrary ISO C data types. OSSP
+xds consists of three components: the generic encoding and decoding
+framework, a set of shipped engines to encode and decode values in
+certain existing formats (Sun RPC/XDR and XDS/XML are currently
+provided), and a run-time context, which is used to manage buffers,
+registered engines, etc. The library is designed to allow fully
+recursive and efficient encoding/decoding of arbitrary nested data.
<h2>Documentation</h2>
|
|
