I loved the literate programming style and the cleanliness of the FFI also.
Org-mode is even more useful than I had previously thought, the http://orgmode.org/worg/org-contrib/babel/intro.html Babel addition also has a wonderful introduction and looks like an extremely powerful way of presenting code and commentary.
Part 4 is probably the most fascinating piece, as it discusses how their technical choices were different from their competitors and how the leveraged those differences.
The sqlite test suite is a fantastic example of how to produce solid software. I wish it were used as a case study for all software engineering courses.
I've had to up the maximum simultaneous connections, but otherwise I've been able to log extremely large volumes of data from 1,000s of machines, with syslog-ng. I'd assume the same is true with rsyslog.
Looking at limits on open files, and considering tcp timeouts and cookies were all we needed. Total volume was in the order of high 10s of GB.
If you want to unpack offline, contact details are in my profile.
Regular expressions are my favourite secret weapon; So many problems are made simple by regular expressions and so few people (outside of IT) know of them.
After I recommended the Sed & Awk book here a few months ago, silentbicycle countered[1] that The Awk Programming Language[2] (by Aho, Kernighan and Weinberger) was much better.
I was curious enough that I bought and read it just at the end of summer. It really is excellent. Highly, highly recommended.
from what i remember, "the unix programming environment" by pike et al is also pretty good, and contains a basic introduction to most of the unix utilities.
You can't go wrong with any programming books Brian Kernighan co-wrote, really. I have _The ANSI C Programming Language_ ("K&R"), _The Practice of Programming_, _The AWK Programming Language_, and _The Unix Programming Environment_, and they're all great. Concise, with a lot of depth that reveals itself on repeat reading.
Ieursalimschy's _Programming in Lua_ ("PiL") was written in a similar style. I recommend it quite highly, too. Great language, great programming book.
Also, the PSD, SMM, and USD books (_4.4BSD Programmer's Supplementary Documents_, etc.) are dry, but also have excellent introductions to several classic Unix tools. They're included as documentation in some BSD installations, and should be easy to find otherwise. The intros to lex and yacc are particularly good.
I'm glad you saw this thread. It's always nice to find out somebody actually paid attention to (and appreciated) some advice you put out on the interwebs.
An application is a software product which fulfills a useful purpose (performing a task, storing data, etc.)
An enterprise application is an application which is suitable for use in a wide variety of environments seen in companies. (for example, as a point of difference, an enterprise application might support a wider variety of platforms or data, or at greater scale than a non-enterprise application)
What about collection of different applications which is inter-dependent with each other. Each application must be communicable and extensible with less pain. That's what in my mind for enterprise right now..
Enterprise extensibility and inter-operativity or inter-dependency is extremely complex to get right.
Multiple standards exist for just about anything, and most implementations of something are broken in one way or another. I've seen obvious and subtle breakage in things that ought to be simple:
* timestamps (not unambigious, not including timezone data)
* mac addresses (within SNMP, in a variety of formats in different places on the same kit)
* integration with LDAP (group membership only looking at primary membership)
* etc.
