[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OT: Re: [Chicken-users] rails-like framework

From: john
Subject: Re: OT: Re: [Chicken-users] rails-like framework
Date: Thu, 27 Apr 2006 12:20:01 +0100

With ASN.1 there is a separation between how the protocol is described and how it is represented "on the wire". As the other John mentioned, depending on application requirements you can choose different encoding techniques. Ones like Basic Encoding Rules (BER) encode a "tag" structure together with the values. Packed Encoding Rules (PER) attempts to send the minimum amount of data so does not encode this structure. Although this concise encoding is a little less flexible the values encoded may still be optional and you may send them in any order if you use the right datatype.


On 27/04/06, Shawn Rutledge <address@hidden> wrote:
On 4/25/06, John Cowan <address@hidden> wrote:
> In that case you might as well use ASN.1, which has the advantage of
> being an international standard with multiple data representations
> available (including a textual one).  IMHO there is little point in
> concocting yet another binary representation of XML.

What I don't like about ASN.1 is the data is not self-describing - you
need to specify a sort of schema or IDL which defines the parameters
in the messages, and then at runtime the assignment of actual
parameters to formal ones is positional, right?  The design becomes
way too rigid and brittle - you can't add or remove parameters, or
give them in the wrong order, and you can't intercept a message and
decipher it without the schema.  Maybe you could use it for simple
remote function calls though - let the Scheme function definition
drive the message format.

Chicken-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]