-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/05/2010 11:06 AM, M. Ranganathan wrote:
> On Tue, May 19, 2009 at 1:57 PM, Marc Petit-Huguenin <[email protected]> wrote:
>> Alex Balashov wrote:
>>> The RFCs are fairly
>>>
>>>> Any of you are aware of literature on how to write SIP stacks besides the
>>>> documentation provided by open source SIP stacks?
>>>
>>> The RFCs are fairly exacting and rigourous on the topic of the layers of
>>> abstraction required on the implementational level.
>>>
>>
>> Honestly, reading an RFC is not a simple task, and it's an
>> especially daunting task when considering the huge number of RFC
>> that need to be read and understood to even think to start writing a
>> SIP stack (I mean a professional grade SIP stack, not the toy stacks
>> that you can download on the Internet).
>
> There are a handful of very good SIP Stacks that one can download on
> the Internet. What exactly is a "toy stack" ? Is it a stack that is used in
> SIP toys?
toy
n 1: an artifact designed to be played with [syn: {plaything}]
2: a nonfunctional replica of something else (frequently used
as a modifier); "a toy stove"
3: copy that reproduces something in greatly reduced size [syn:
{miniature}]
The 3 definitions probably apply.
- --
Marc Petit-Huguenin
Personal email: [email protected]
Professional email: [email protected]
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkyrenEACgkQ9RoMZyVa61ej0wCggURE6YKTH5biBXBfxRyJ6WYy
LMEAoIHtMNWbT7EfWWAMdnbETppt6OQD
=6hdg
-----END PGP SIGNATURE-----
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
