From: Peter Hickman <peter@...>
Date: 2004-01-31T02:23:28+09:00
Subject: Re: Learning Curve Development Time Question

Zach Dennis wrote:

>I am curious what others have found with a learning and development curve
>with areas of code that are quite similar.
>
>In the design of a small scale project there will be 2 main systems. Inside
>of these systems will be a few more smaller subsystems. The systems will
>communicate to eachother via network socket interfaces. This is so we can
>have the systems to different machines. I was thinking for expandability
>purposes that perhaps we made the subsystems work the same way. So that if
>for any reason we found one area getting used a ton that we could move it to
>it's own machine with little effort. Since the 2 main systems would need
>socket interfaces to communicate with eachother I am curious if coding the
>subsystems would provide unneccessary development time. Or if since the same
>logic could be applied that was already coded and tested in the 2 main
>systems that the development time may not be unneccessary.
>
>In any of your experiences is this the case? Would the development time for
>the subsystems go way down since the main 2 systems have been tested and is
>good to go? Or since they are different "systems" would the
>learning/development curve still be just as steep?
>
>Thanks for any replies!
>
>Zach
>
>
>  
>
Having two systems talk across a network is not to big a deal but at 
what level do they need to communicate. Could the whole socket thing be 
replaced by http requests? This would allow you to step back from socket 
programming and use things like Webrick.

Just a thought.