Re: Using a single JVM

[David Gibbs <david@xxxxxxxxxxxx>]

Joe Pluta wrote:
> Another option that's really powerful is to use a web application
> server to expose business logic as web services, either via SOAP or
> REST (I prefer the latter for intracompany work). Let the application
> server handle all of the session management issues. You also get the
> benefit of being able to share logic with other business units if
> needed.

In general, I agree with Joe on this.  

As with all implementations, you need to take the context into account.

If the application is highly focused and not likely to be shared with applications on other systems, I think the data queue method is probably easier.

A web service approach is much more flexible and reusable ... but probably more difficult to implement and use in RPG.  It's _much_ easier to use in other languages though (java, php, .net, etc).

The key thing to consider is: think about where and how your application is going to be used down the road and choose the best solution with that target in mind.

david