• 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: Packaging a WO Application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Packaging a WO Application


  • Subject: Re: Packaging a WO Application
  • From: Art Isbell <email@hidden>
  • Date: Sat, 19 Jun 2004 12:17:29 -1000

On Jun 19, 2004, at 3:51 AM, Lotsa Cabo wrote:

I love
what WO provides from a design and development standpoint, but the
requirements are to build a web-based app that can be picked up and
moved to any box WITHOUT a dependancy on a third-party application,
other than the web server and database.

... and an application server.

So, in theory, I should be
able to install a copy of RedHat, throw on Apache and Tomcat and be
good to go.

All of these are open-source technologies. WO is not open-source, so you must pay a license fee to deploy WO apps. You can't turn WO into an open-source product by using some repackaging scheme.


Or, in a M$ world, install IIS and whatever extension I
need to interpret the page language (JSP, etc.).

M$ "gives away" some of their technologies in order to tie users to their platform where they will eventually realize revenue in one way or another. Apple includes a WO deployment license with OS X Server, but that's only valid under OS X Server.


My goal is to be able to build an application that is re-sellable.  I
cannot expect my client to want to purchase a WO license in addition to
my product.  Of course they will need a physical server and web server
software.  Of course they will need to select a database.

If your customers require 100% open-source software, then they can't deploy WO apps.


Other than
that, it does not make much sense to build something in such a way that
they will be forced to license additional products.

How about ease of development that WO offers? If you're limited to open-source application server development, then you and your customers will have to expect development to be more arduous, time-consuming, etc. There is still no free lunch.


Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Packaging a WO Application
      • From: Hunter Hillegas <email@hidden>
References: 
 >Packaging a WO Application (From: Lotsa Cabo <email@hidden>)
 >Re: Packaging a WO Application (From: Art Isbell <email@hidden>)
 >Re: Packaging a WO Application (From: Lotsa Cabo <email@hidden>)
 >Re: Packaging a WO Application (From: Michael Engelhart <email@hidden>)
 >Re: Packaging a WO Application (From: Lotsa Cabo <email@hidden>)

  • Prev by Date: totally stumped 2...
  • Next by Date: Re: totally stumped 2...
  • Previous by thread: Re: Packaging a WO Application
  • Next by thread: Re: Packaging a WO Application
  • Index(es):
    • Date
    • Thread