On Saturday 13 April 2002 09:43 am, Paul Hammant wrote: > Whist it is feshest in your mind, what was the hardest thing for you to > grasp, or the moment of most revelation as you navigated from AltRMI > newbie to adept? It will be useful as I work on the the docs.
Hardest thing? The architecture! I'm one of those that likes to learn by examining the code and there are many layers to go through due to the different transports. Once I started to get a grasp on that things became easier. Having real javadocs on methods would be a great help on that. (I might tackle that if i get bored, might be a good way to collaboratively create the docs). Otherwise its actually pretty simple once you get down to it. I will be donating the component wrappers I have for altrmi, I just want to bang on them a bit and put some docs on them first, I should have a patch sometime this week. One thing I have noticed whilst running my program at home (the database is at work across the internet on a 256k connection and thus some operations take a long time, or large queries take a while to come back) is that long operations will time out on the socket (more than a minute, will changing AbstractSocketStreamInvocationHandler.makeSocket() fix that?) Also unused connections in the pool will return a 'Broken Pipe' error when reused after a period of inactivity. I thought the pinging code would handle that but perhaps it isn't fully hooked up yet? Its not a problem as I have a wrapper on lookup() that retries on a new AltrmiInterfaceLookup if an AltrmiInvocationException is received. But now that things are mostly working I will probably begin testing same-JVM operations (the ultimate goal) -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
