Forcing the other side to do something that is not defined in the IDL requires changing the wire format, which is something we should try to avoid unless it provides big benefits. You also have to consider the fact that the "other side" could be running a language that doesn't support order-preserving maps. However, I mentioned the possibility of annotating a type to use an ordered map. It would be as easy to force it to use an order-preserving map, if available.
--David Yonik Seeley wrote: > On Tue, Sep 9, 2008 at 1:45 PM, David Reiss <[EMAIL PROTECTED]> wrote: >> I'm fine with implementing compareTo. With proper type annotations, >> we could provide a way to define that a given map be instantiated as >> a TreeMap instead of a HashMap when deserializing, which would enforce >> an order. > > How about retaining an order... if LinkedHashMap is used on one side > when order is important, is it possible to force creation of an order > preserving map (like LinkedHashMap) on the receiver? > > -Yonik >
