On Mar 18, 2008, at 11:13 AM, Mike Heath wrote:
Alan Cabrera wrote:
On Mar 1, 2008, at 10:43 PM, Alan D. Cabrera wrote:
On Feb 29, 2008, at 2:55 PM, Mike Heath wrote:
Alan D. Cabrera wrote:
So, HCF can be optional. If you create HCs directly any cookies
that
are created are scoped w/ that client. The HCF would take an
implementation of a CookieManager (CM) interface. I guess HC
could as
well.
That's how I've designed my API. The HCF has a configure CM and
the HC
can have it's own CM if that's desired.
I don't have explicit support for CookieManager chaining though.
I'll
have to add that.
What is CM chaining?
Still curious.
We discussed the idea of having a parent CM and a child CM would store
its own cookies but if id didn't have a cookie it would look to its
parent for the cookie. This is what I was referring to when I said
"CM
chaining". I was indicating that it may be a good idea to add
explicit
support to the client API for this type of parent/child relationship.
I'm going to move the API we've been discussing to my sandbox so
everyone can peruse the code and we can better discuss these ideas and
start implementing them. I've made a number of changes that I'm
anxious
to get feedback on.
What use case does this support? It really strikes me as odd.
But, I guess it doesn't matter so long as the parent paradigm doesn't
sneak into the CM interface.
Regards,
Alan
