Hello Lisp users
I need to develop a prototype of an application which, among other,
encode and decode SIP messages (RFC 3261 http://www.ietf.org/rfc/rfc3261.txt).
The definitions are given in a ABNF format, but I do not necessarily
needs a direct translation from ABNF to classes
Lisp have many alternatives to do that, starting from develop a parser
from scratch or use ready made packages.
I'm looking for the practical, quickest solution I can find.
I would appreciate some direction from engineer which has some
expression with similar tasks.
Thanks
Tzach
<··············@gmail.com> wrote:
+---------------
| I need to develop a prototype of an application which, among other,
| encode and decode SIP messages (RFC 3261 http://www.ietf.org/rfc/rfc3261.txt).
|
| The definitions are given in a ABNF format, but I do not necessarily
| needs a direct translation from ABNF to classes
| Lisp have many alternatives to do that, starting from develop a parser
| from scratch or use ready made packages.
| I'm looking for the practical, quickest solution I can find.
+---------------
Since, as RFC 3261 says, SIP Request and Response messages "use the
basic format of RFC 2822", and since "Except for the above difference
in character sets, much of SIP's message and header field syntax
is identical to HTTP/1.1", I'd start with any old Lisp library you
have handy which knows how to read mail or HTTP headers -- especially
mail headers, since there are things in SIP that closely resemble
email addresses -- then tweak it for the syntactic differences of SIP.
Some possible places to start looking:
http://www.cliki.net/rfc2822
http://www.cliki.net/mel-base
http://www.cliki.net/CL-MIME
-Rob
-----
Rob Warnock <····@rpw3.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607
On Feb 10, 1:43 pm, ····@rpw3.org (Rob Warnock) wrote:
> <··············@gmail.com> wrote:
>
> +---------------
> | I need to develop a prototype of an application which, among other,
> | encode and decode SIP messages (RFC 3261http://www.ietf.org/rfc/rfc3261.txt).
> |
> | The definitions are given in a ABNF format, but I do not necessarily
> | needs a direct translation from ABNF to classes
> | Lisp have many alternatives to do that, starting from develop a parser
> | from scratch or use ready made packages.
> | I'm looking for the practical, quickest solution I can find.
> +---------------
>
> Since, as RFC 3261 says, SIP Request and Response messages "use the
> basic format of RFC 2822", and since "Except for the above difference
> in character sets, much of SIP's message and header field syntax
> is identical to HTTP/1.1", I'd start with any old Lisp library you
> have handy which knows how to read mail or HTTP headers -- especially
> mail headers, since there are things in SIP that closely resemble
> email addresses -- then tweak it for the syntactic differences of SIP.
>
> Some possible places to start looking:
>
> http://www.cliki.net/rfc2822
> http://www.cliki.net/mel-base
> http://www.cliki.net/CL-MIME
>
> -Rob
>
> -----
> Rob Warnock <····@rpw3.org>
> 627 26th Avenue <URL:http://rpw3.org/>
> San Mateo, CA 94403 (650)572-2607
Thanks. I will look into these packages.
- Tzach
From: Sohail Somani
Subject: Re: Practical encoding / decoding of text format
Date:
Message-ID: <qbyrj.18662$w57.6826@edtnps90>
On Sat, 09 Feb 2008 22:56:54 -0800, tzach.livyatan wrote:
> ABNF format
What the heck is ABNF?
--
Sohail Somani
http://uint32t.blogspot.com
From: vanekl
Subject: Re: Practical encoding / decoding of text format
Date:
Message-ID: <fomb90$nkk$1@aioe.org>
Sohail Somani wrote:
> On Sat, 09 Feb 2008 22:56:54 -0800, tzach.livyatan wrote:
>
>> ABNF format
>
> What the heck is ABNF?
>
ftp://ftp.rfc-editor.org/in-notes/rfc4234.txt
··············@gmail.com writes:
> Hello Lisp users
> I need to develop a prototype of an application which, among other,
> encode and decode SIP messages (RFC 3261 http://www.ietf.org/rfc/rfc3261.txt).
>
> The definitions are given in a ABNF format, but I do not necessarily
> needs a direct translation from ABNF to classes
> Lisp have many alternatives to do that, starting from develop a parser
> from scratch or use ready made packages.
> I'm looking for the practical, quickest solution I can find.
>
> I would appreciate some direction from engineer which has some
> expression with similar tasks.
It looks like standard "key: value" headers. You could check how
they're parsed in the various packages implementing rfc822.
Also have a look at http://www.cliki.net/Etiquette
--
__Pascal Bourguignon__ http://www.informatimago.com/
Cats meow out of angst
"Thumbs! If only we had thumbs!
We could break so much!"