|
On 5/15/06, Brad Stone <brad@xxxxxxxxxxxx> wrote:
On Sat, 13 May 2006 16:46:31 -0500 "albartell" <albartell@xxxxxxxxx> wrote: > The thing to remember is HOW you do things in Java will > usually make or > break it. True, but it still seems when this argument comes up you always hear best case Java vs. worst case RPG comparisons, and the same things like "scalability"... I missed the thread you referred to as well so I'm interested in that, as well as explanations of multithreading. We all will tout what we already use and/or benefit from others using. So test drive them both and see for yourself which is the best fit for your situation.
Definitely a good idea. Now that it seems that Apache may have handled some of the issues with CGI (although I'm not sure about thread synchronization issues), performance may not be the deciding factor. Availability of developers, however, may be a deciding factor. Consider this... If you are up for a promotion, how easy will it be to find someone to fill your shoes? I still think it's going to be easier to find Java/PHP/.NET developers than RPG developers. I am having a devil of a time finding RPG developers, and all I want them to do is write batch RPG programs that we can call from Java. I don't need anything as specialized as RPG-CGI. Mike E.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.