tag:blogger.com,1999:blog-7831813422886730737.post5879588484875162581..comments2023-10-08T10:44:28.524+03:00Comments on Event Processing Thinking: On hard coding event processing functionalityOpher Etzionhttp://www.blogger.com/profile/10791357917675270335noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7831813422886730737.post-58212564820357337762009-07-03T19:30:48.229+03:002009-07-03T19:30:48.229+03:00My youngest daughter asked me to correcet this pos...My youngest daughter asked me to correcet this posting -- actually, two of my four duaghters did remember my birthday, but mentioned it to me later that evening... after I wrote this posting... Well -- I decided to record her request as a comment.<br /><br />cheers,<br /><br />OpherOpher Etzionhttps://www.blogger.com/profile/17070103285719046013noreply@blogger.comtag:blogger.com,1999:blog-7831813422886730737.post-60247658265483940992009-06-30T09:19:32.442+03:002009-06-30T09:19:32.442+03:00I have this kind of discussions several times ever...I have this kind of discussions several times every week. Event processing logic is fun to code, so there's always tons of arguments to do it yourself. The developers that appreciate a COTS product for this kind of problems tends to be those ones which have been involved in trying to maintain a code base with lots of realtime processing. Badly designed multi-threaded apps with lots of tweaks seems to be rather pain to maintain...Mhttps://www.blogger.com/profile/15928652667178672308noreply@blogger.com