Based on the message I keep getting while reading this list, I am in the process of reorganizing an application that has more runmodes than I'll publicly admit packed into a mega-module. Despite the headaches of refactoring, I'm beginning to see the benefits of splitting up my modules into many small pieces and am even starting to see where to make the splits. However, in splitting up the module, I'm finding that redirecting users to other parts of the application has become more complicated than simply returning the desired subroutine. When needing to redirect a user from one script to another, is the standard practice to use a redirect? For instance, I have a module that handles several administrator functions (Admin.pm). In addition, I need the administrator to be able to manage user records. Since I can forsee new runmodes being added to the Admin module over time, I decided to break out the user records management which has the modes (BREAD/CRUD/etc.) into a separate module (UserManager.pm). An administrator accesses the user manager by doing a search from the admin page which returns a list of matching records. If no records match, I used to return the user to the admin menu with a message. Since the search is now being handled by the UserManager, if no records are found I have to do a redirect to get the user back to the admin menu with an appropriate error. I'm realizing that some of this is just rethinking how I structure my application. Any suggestions would be most helpful. Thanks! William -- Lead Developer Knowmad Services Inc. || Internet Applications & Database Integration http://www.knowmad.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.