in reply to Re^3: Seeking design improvements for Perl code library remote server
in thread Seeking design improvements for Perl code library remote server

Well, I procrastinated until now with looking into the details of the suggested code. Now that I'm really looking, not being a Perl guru, I'm confused with how the breakdown of the code is between the backend and the server interface. I was thinking of having the server (frontend) component be packaged as RobotRemoteServer::Server or keep it as RobotRemoteServer as it originally was.

But right now, I don't see how the backend links to the frontend in the suggested code in terms of things like using statements (to use front/back end package in the other) along with how the actual object instance shares method & properties between the packages.

Can you/someone elaborate? FYI, I've never built multi-file packages, only single file contained packages.

  • Comment on Re^4: Seeking design improvements for Perl code library remote server

Replies are listed 'Best First'.
Re^5: Seeking design improvements for Perl code library remote server
by Anonymous Monk on Feb 10, 2015 at 08:55 UTC