From: Dean M. B. <mik...@gm...> - 2010-08-24 10:33:55
|
On Sat, Aug 21, 2010 at 5:22 AM, Glyn Matthews <gly...@gm...> wrote: > Hi Dean, > > On 20 August 2010 12:03, Dean Michael Berris <mik...@gm...> wrote: >> >> I found one good hack to make the directives more generic and more >> tied into the async-friendly messages. I've implemented it locally and >> am in the process of gutting every directive we've ever written (I >> really need to learn preprocessor metaprogramming at some point to >> make this easier). >> > > Cool, this is what I need because I'm a little blocked. Let me know when > you have something that I can play with and I'll take a look. And you might have to wait a little longer. Now the problem I'm reaching is the consequence of the Request concept applying to both asynchronous and synchronous request objects. The Request concept refines the Message concept, which defines some primitive operations to be defined. Now I've added modifiers to the requirement on the Message concept, which means creating messages just got a little "harder" and more involved. Maybe at some point I'm just going to make a Directive concept too. I'm learning that generic programming is a little more involved (but really safe) and thus fun to implement. ;) -- Dean Michael Berris deanberris.com |