[cgiapp] Re: Preview Release available with callbacks code integrated

[Mark Stosberg <suppressed>]

On 2004-12-20, Cees Hek <suppressed> wrote:
>
> The problem comes when two developers want to run two different things
> at the same stage.  Using the sub-classing technique works fine when
> working on a project by yourself, but we are trying to solve a problem
> for people that want to distribute modules (or plugins) for others to
> use.

I think it would be useful to show a complete example. As I've thought
through it more, I think I've re-confused myself about how it would work.

At what stage in the process do callbacks get registered? It seems
obvious that they must be registered before they called. So when would
you have a chance to register one that would run in cgiapp_init?

After you have called new(), it's too late.

Would plug-in users be adding code like this to cgiapp_init?

  $self->add_callback('prerun', \&callback);

If you have to explicitly add the callbacks to your code (as a
plugin-user), it seems like it defeats the point, since you could just
call the callback method directly at that point.

I'm sorry I'm muddled about this-- yesterday I thought I knew exactly
what I was getting into. :) 

    Mark

-- 
http://mark.stosberg.com/ 


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed