Stephen J. Turnbull wrote:
Current Mule, it's hard to even pass a sane value for where an
happened because of the layers on layers of buffering in coding
This has nothing to do with whether it's written in C or Python and
everything to do with the buffering, which would be the same in either case.
Ben> well, take a look. my verbal descriptions are often
Ben> because it's difficult for me to type long, detailed emails.
Ben> but i keep feeling like you are worried about issues i'm
Ben> already dealing with.
Could be. But it's quite clear you're more worried about maintaining
Mule compatibility and efficiency for 50MB buffers than about getting
the cleanest possible design in front of the reviewers and testers as
quickly as possible.
all right, stephen, i've had enough; you're really starting to piss me
off. the only thing that's really "quite clear" is that you haven't
bothered to actually read any of the code i've written. please go do
that, then come back to me with *specific* issues referring to *actual*
code, and i'll be glad to discuss them.