abdera-dev mailing list archives

Garrett Rooney wrote:
>> [snip]
>> Mainly because the code is currently embarrassingly sloppy and I really
>> just started working on it in earnest yesterday morning.
>
> Ahh, ok.
>
There's madness to my method, for sure. :-)
>> [snip]
>> Likely not. There are two motivations: 1. allow for other underlying
>> client stack impls (e.g. something other than commons httpclient) and 2.
>> align with the model used by the rest of Abdera. We likely should take
>> a look at the model used across the entire code and see if a better
>> approach can be applied across the board.
>
> I just worry that it's less likely that you'd want to switch http
> client impls than underlying XML parsers. The only particularly
> interesting reason I can think of to switch http clients might be to
> use something like AsyncWeb, and allowing that would likely require a
> rather different API than something like commons httpclient...
>
You're likely right here and it would greatly simplify the code if we
just said, "We're writing code for the Commons client, period.", which
is fine for me.
- James