From: Andrew H. <hu...@ll...> - 2003-06-05 15:50:35
|
At 11:14 PM 6/4/2003 -0400, Chris Winters wrote: >Andrew Hurst wrote: >>I'm interested, and we might use it for an internal application here, but >>it remains to be seen if we can use it or not. "I'm not totally >>convinced to use OI yet" -- my boss. We might use Oracle Forms instead :( > >Whenever I think OI is heavyweight I look at something like that and >breathe a sigh of relief :-) Yeah, its rather large. It is quick to get things developed, but thats not the problem I have with it. Its that its a PL/SQL client side application (I think C underneath) and the web enabled version just puts a Java "face" on it. So its rather difficult (in my experience) to really leverage the features of http well. Also, writing complex logic in PL/SQL sucks :) Nothing like doing in 10 lines of PL/SQL what 1 line of perl can do. >Let me know if I can help with any convincing. Thanks for the offer. I might end up writing a comparison/contrast of the two (unbiased, of course ;) to see which fits more for our situation. I might ask for some input then. The main deal I think my boss has with OI is the licensing. He's all for Open Source, but the problem is giving the changes back. We probably won't be distributing it, so that wouldn't be an issue. But if I make good changes / add features I'm going to do what I can do get them back in the main tree even though the license doesn't call for it. To do that, requires a code audit though from a few tech guys, for obvious reasons (national security, etc). Yes even for simple web apps. Its a rather arduous process. I'll keep you posted on the developments here... -Andrew >Chris > >-- >Chris Winters (ch...@cw...) >Building enterprise-capable snack solutions since 1988. |