|
I am currently reading the RFCs 3195[^] (BSD syslog protocol) and 5424[^](syslog architecture) for a project at work, we need syslog functionalities due to federal comlpliance guidelines in the medicine sector.
One may say "That's boring", but I somehow like it. I got the responsibility for one of the most important parts of the project (not bad for a barely 20 years old apprentice), and I am running under full power reading through all these RFCs and get a syslog library up and running by myself (I'll even use the correct layering and terminology to get it as near as possible to the Linux syslog).
I am sorry for you guys out there, no article this time since it is work-related (and I do it at work).
Anyways, if I find a peer or two to do the same thing in a bit of spare time off-work I might think about doing this a second time to put it up here.
|
|
|
|
|
For a "better" way to do "diggin'"  , checkout the sample "HTTP protocol" RFC representation Here[^]. If you feel like it, please let me know by voting it up, we might put some of them into our structured documentation repository if enough interests exists. Thanks.
(Note: html5 is generated so a proper browser is needed to have a better view)
Having way too many emails to deal with? Try our SQLized solution: Email Aggregation Manager[ ^] which gets your email sorted, found and organized beyond known precision.
|
|
|
|
|
Hi,
Thanks for the input. What I am planning is writing an actual syslog server and client including the relais, collectors, originators and so on in c++ / Qt.
Let me know if you are still interested.
|
|
|
|
|
Yeh, I know what you are planning. What I am suggesting could save you great deal of time spent on scrolling the document ...
Having way too many emails to deal with? Try our SQLized solution: Email Aggregation Manager[ ^] which gets your email sorted, found and organized beyond known precision.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
