The table of content looks great. The cookbook style I am more acustomed to is based on question/solution, i.e., how/what to do. The HOWs usually have purposes within a given context.
e.g., "Working around NAT" is not a question type and the context is so wide it almost has no context and a purpose is not obvious if any. I would prefer to see something like e.g., How to configure NAT for SIP in Asterisk 1.4 + fronted by a firewall when there is a one-way or no comminucation after successful registration. I am sure there are enough postings from this group to start with... my 2 cents! Thanks, Richard ----- Original Message ----- From: "Leif Madsen" <[EMAIL PROTECTED]> To: "Richard (Rogers @ work)" <[EMAIL PROTECTED]> Cc: "Jim Van Meggelen" <[EMAIL PROTECTED]>; "John Oladehinde" <[EMAIL PROTECTED]>; <[email protected]> Sent: Tuesday, July 24, 2007 1:09 PM Subject: Re: [on-asterisk] Future of Telephony 2ed. > Awesome! Contributions welcome :) > > http://www.asteriskcookbook.com > > Writing a book is a very time consuming, non-glorious, and highly > underpaid adventure, so unfortunately it's one thing at a time, and we > figured a 2nd edition of TFoT was needed to cover 1.4. We'll be > starting to work on the cookbook shortly I think once we've had a bit > of a brain break from TFoT2 :) > > > On 7/24/07, Richard (Rogers @ work) <[EMAIL PROTECTED]> wrote: > > A cookbook is better in my view - its more practical than a reference... > > > -- > Leif Madsen. > http://www.leifmadsen.com > http://www.oreilly.com/catalog/asterisk > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
