This is just an observation, but my experience is that if you start out focusing on implementation details before you understsnd at a high level what it is that you want to accomplish, it's easy to ind yourself in a quagmire, making no real progress. Questions like "Should I use e-mail, HL7 or wb services for message transport?" are simply NOT THAT IMPORTANT, and they can wait until you've figured out what the content of your messages needs to be. I know it's tempting to look at an existing module that seems close to what you want and then start focusing on implementation details, but that's seldom a good idea. In order to be successful, you really need to focus on understanding what it is you're trying to do, and put matters of execution on the back burner until you reach the point that those kinds of low level decisions really do need to be made (which is probably later in the process than you think). If you don't, you'll find yourself overwhelmed with mostly irrelevant information, and it will be very difficult, even to guess what needs to be done next.
=== Gregory Woodhouse <[EMAIL PROTECTED]> "All truth passes through three stages: First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." --Arthur Schopenhauer ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
