We don't bite newbies here... much | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
web app ...~10 small scripts for the UI to interact with....I'm wondering if a single script would be viewed as the clearer approach... I already have a couple of modules with major functions in them, but for execution what would you monks recommend, a larger script with control statements or several smaller scripts like I'm using now? The "web app" deals with urls not scripts, so to the web app , its all the same one script per url is pretty common organizational scheme , script as an API but to a human moving an app from one machine to another, one script to update versus ten scripts to update ... shared config file ... it is all about the same :) But to a human writing a test suite, APIs are the natural choice, but scripts aren't an obstacle, just one step and a few mouse clicks removed, an extra fork/system call so, most of the modern web apps, mojo/dancer2/... favor one script that loads modules that register path/url handlers .... because programmers write subs and put them in modules and call it an API, that is the basic organizational structure for programmers In reply to Re: Good Style for Small Apps ( one script versus many )
by Anonymous Monk
|
|