Jump to content

Recommended Posts

Ya I thought I understood you, but let me see if I get it...

 

you have :

 

A1 implements Observer watching...

Observable A2 implements Observer which might be watching

Observable A3

 

Or something other combination like that.  There's no reason not to do it.  I'm not sure what you mean by normal, though.  If you're asking if it's a bad design decision I would say it doesn't sound like one, but I would need to know more about what your'e doing.

 

In my experience it is useful to string templating classes together using the pattern above so that when one part of the view is generated it notifies an observer which is itself an observable, etc, until the final HTML is generated.  I think that is more elegant solution than trying to form the equivalent through composition (so I think it's better design).

 

If you care to share more details I'll try to form more of an opinion.

Link to comment
https://forums.phpfreaks.com/topic/54181-observer-pattern/#findComment-268171
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.