Sometimes Each Case is Different

There are situations in which we can't avoid working out the classes from scratch for each client and server, and sometimes we may not mind.

 o Basic data types are almost universal
Basic data types, such as individual numbers and strings, will be part of the fundamental interface nearly everywhere. But how much interesting data only requires these?

 o Some data types are too bizarre to import.
For example, result sets from SQL queries are only really useful to hand back to another DBMS method.

And the special forms used in some numerical computations (e.g., matrix decompositions) only make sense to related computations. Either both systems share the same grubby representation (and know it) or you do all the computations in one system.

It might be possible to push the first case to, say, sequences of basic types and a few other "obvious" examples. But already, we're in need of a more explicit approach.


An Example A Proposal Start
Last modified: Sun Jul 5 18:26:11 EDT 1998
© Lucent Technologies.