Doug I would always recommend calling subroutines on the server, unless you have a pressing need not to do so.
The biggest gain is for quality - it is much better to write and QA the back end code first, then write the interface code. That way you can work in the sure knowledge of the quality of the expected results, which makes debugging much easier should something go wrong - and you can create test routines for regression testing should things change. It also means any business logic does not get fragmented: good practice always dictates that any business logic should exist only once and in one location, so anything that could be shared between your client and any new or existing server code should be kept neatly packaged on the server - which is what a subroutine is for. I've posted before about having a single, centralized dispatch routine and a standard interface for client-facing subroutines: this adds a tiny overheads but makes it easier to put in logging, recording and playback of the calls. Brian -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of doug chanco Sent: 14 March 2011 02:14 To: U2 Users List Subject: Re: [U2] Uniobjects and java thanks,can you give me some of the pros/con's? I have some ideas, (not passing huge amounts of data back and forth for one) but I'd be interested in hearing others, for the moment I think I will be calling subroutines but maybe down the road that may change (if the benefits out weigh a subroutine call) Currently all I think I will be doing initially is just getting data from universe dougc On 3/11/2011 4:09 PM, Symeon Breen wrote: > Also think about how your app works - There are two ways of using uniobjects > - you can just use it to call a sub and the sub does all the work and > returns the data that you need (a quick in and out), or you can do all the > file and record manipulation in the java layer. They both have pros and > cons, the important concept is how long do you want to hold on to your > connection into u2 for. Bearing in mind licencing issues, pooling etc. > > > > > > Rgds > > Symeon. > listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
