Hi, Kathey. My background is definitely on the networking/runtime side more than in database internals. I looked at the NetworkServer and was a little daunted. It didn't help that there was no client code to look at, but that has recently changed.

I humbly request that I try to do some simple little patches (although look at my last attempt to find something simple :) ), I can focus on NetworkServer small patches, and start getting comfortable with the code. Perhaps we can do some email exchanges where you help me through the architecture of the NetworkServer, it was a little hard to follow.

David

Kathey Marsden wrote:

Firstly, I would like to say that I am so happy that this little bug
brought such big thinkers to Network Server.

David Van Couvering wrote:


I agree with you that there is a bit too many responsibilities for one
object



I think that this is highly prevalent issue with Network Server in
general. For instance, I think clearly the parameter metadata needs to
be separated out from DRDAStatement and the respnosibilities of DRDAConnThread are quite immense and probably need to be evaluated and
delegated accordingly. I have lacked the time and confidence to go in
and tear these things apart and put them back together. I hope you
will consider sticking around Network Server for a while. It's seems
to me you have been shopping around for a place to do some good and I
think you could really make a big difference here. If so, I would
like to facilitate in any way I can, but we should pick that up on a new
thread #:)



Thanks

Kathey





Reply via email to