I'm aware that it's probably that I might need to refactor some things ...
However, I'm not sure the ideal way to have certain bindings, without replacing them. I have one binding, Caller, which is literally just a string explaining what root service called an object. This way I can trace things like how an HTTP request originated. By default, it's unknown... because any library should be able to perform an HTTP request if necessary. However, I need to swap in a new one as I'm starting up certain tasks. So if I have a Foo and a Bar task each should have its own Caller. And yes, you might be right... I may need to rethink some of my bindings... some of these aren't completely obvious though. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-guice+unsubscr...@googlegroups.com. To post to this group, send email to google-guice@googlegroups.com. Visit this group at http://groups.google.com/group/google-guice. To view this discussion on the web visit https://groups.google.com/d/msgid/google-guice/41e3b741-ec9b-49a2-bebe-b8881bd48aa7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
