• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Does switching to servlet deployment serve a purpose?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Does switching to servlet deployment serve a purpose?


  • Subject: Re: Does switching to servlet deployment serve a purpose?
  • From: Dov Rosenberg <email@hidden>
  • Date: Mon, 01 Feb 2010 17:22:29 -0500
  • Thread-topic: Does switching to servlet deployment serve a purpose?

Politics was our biggest motivator. Our software is deployed on customers
servers and it was not an option to install a WO runtime everywhere. Its not
ideal but deploying in a Tomcat type environment seems to work pretty well
even when our app is scaled to pretty high loads

Dov


On 2/1/10 2:51 PM, "Hugi Thordarson" <email@hidden> wrote:

>>> The biggest things you lose is the built in load balancing and the
>>> javamonitor. You will need to spawn your own instances and load balance them
>>> externally.
>>
>> That seems like a rather big drawback.
>
> Indeed. I have however not checked out how this is handled by Glassfish. I
> imagine there must be some sort of a load balancing architecture somewhere,
> however.
>
>
>>> Deployment turns into a single war file that is easy to do. It is much
>>> easier to deploy a war versus setting up a wo deployment.
>>
>> With the full embedding now available in WOProject, I suspect that a fully
>> embedded .woa may now be easier to deploy.  You do still need to deploy the
>> web server resources in a separate step.
>
> Indeed. We embed everything. And since we're not operating under heavy load,
> we have the luxury of being able to ignore WS resources and just use app
> resources. It's disgusting, I know - but as long as we can spare the cycles...
> :).
>
>
>>> The other big gain is support for non wo supported platforms like Linux,
>>> solaris, and windows
>>
>> The only thing not cross platfom is mod_webobjects and that is fairly easy to
>> build and mDimension kindly hosts several pre-built versions:
>> http://webobjects.mdimension.com/wonder/mod_WebObjects/Apache2.2/
>>
>> From what I have seen, the only real reasons to use servlet deployment are:
>> - access to things like jsp tagging
>> - deployment on hosting services that don't support WO (which would be most
>> of them...)
>> - deployment in a mixed environment where servlet deployment has been
>> mandated as the standard
>>
>> At least as of a couple years ago, ITMS was using standard WO deployment.
>> They need all the bang they can get, so if servlet was better I expect they
>> would have used that.
>
> Yeah, that's pretty much what I figured. As usual, it mostly boils down to
> politics, I can't find any actual technical reasons to switch deployment
> environments.
>
> Thanks!
>
> Cheers,
> - hugi _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Does switching to servlet deployment serve a purpose? (From: Hugi Thordarson <email@hidden>)

  • Prev by Date: Simple Image Button Question
  • Next by Date: Re: New look for wocommunity.org
  • Previous by thread: Re: Does switching to servlet deployment serve a purpose?
  • Next by thread: Re: FrontBase 5
  • Index(es):
    • Date
    • Thread