Also, in searching for code to deal with chunked responses, I came across Apache HttpComponents. I knew something like this existed by Apache but I didn’t realize that it took care of so much for you. Now I’m wondering why the Citrus Framework doesn’t use this to handle HTTP requests. Right now, it uses mostly Spring to handle a fair amount of the configuration and message building, but it doesn’t yet handle chunked responses, at least not that I’m aware of. Now, to code it manually or use massive amounts of code already written? That’s obvious. I should talk with the Citrus developer, get onboard, and see if he has a preference first though, since these changes to the Citrus source would be useful to others too.

For the last week, working through this project, I’ve re-learned and learned quite a lot about HTTP requests, Ant, DTD/XSD, and XPath, and I feel much more comfortable dealing with those now than I did a week ago. It’s a good feeling to have learned and done something new that’s kind of on the cutting edge of things, and to have fun doing so too! Ah, I sound so corny. Anyway, I can’t wait to get more involved with the company that this project is for and delve into some code that has a lot of potential and fun-value. I’m just waiting on approval from the developers now, but so far things look good. Wish me luck! =)