• 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: About instance's integrity.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: About instance's integrity.


  • Subject: Re: About instance's integrity.
  • From: Chuck Hill <email@hidden>
  • Date: Sat, 22 Nov 2008 22:01:23 -0800


On Nov 22, 2008, at 6:01 PM, dododo2020 dododo2020 wrote:

Hello,

My name is Ken. It is my first post to this list.
I had searched many solutions before and Thank you for this list.

I have a question about WO app's instances and their integrity.

I am considering to process multiple http requests by multiple instances of WO app.

Each instance can (and should in most cases) be configured to process multiple simultaneous requests. The simultaneous part becomes single threaded at the point of changes to the object store (usually associated with database access).

When I update some data in db from one instance,the changes can be updated automatically for all the instances?
Or should I notify something to other instances of same app and fetch fresh data manually?


This situation can be occured when developing a site with multiple instances and admin app for the site.
The integrity through the instances are maintained atuomatically by WebObjects?
If it is maintained automatically,is it true for WO app without session ids in URL and with the ids in cookie?


The location of the IDs has no effect on this.
Could anyone answer my questions?

By the way I think WO can still be a main stream tool for Java developers
if WebObjects's core could be opensource


I can confidently assure you that this will not happen.

or replaced by other DAO tool easily and stably.

Why? EOF rocks. I have looked at the other tools and none offer a compelling advantage over WO. One of the real benefits of WO is that is is single source from end to end. There is no need to use frameworks to glue frameworks together to achieve your goals. It is sane, consistent, and mostly free of surprises.


If managing graphs of data and locks are required I would like to do without EnterpriseObject.

Again, why? You are discarding the _best_ part of WebObjects! Why not just use Tapestry and some other frameworks?

I think Implementing WO app with opensource DAO can be productive and high-performence today.

Uh, it is productive and high performance as it is. Adding an open source DAO will only serve to make it worse.

But I would like to use current code by EnterpriseObject if I don't need to manage the integrity of instances manually.



Chuck


-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







_______________________________________________ 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
  • Follow-Ups:
    • Re: About instance's integrity.
      • From: "dododo2020 dododo2020" <email@hidden>
References: 
 >About instance's integrity. (From: "dododo2020 dododo2020" <email@hidden>)

  • Prev by Date: Re: About instance's integrity.
  • Next by Date: Two questions about latest build system
  • Previous by thread: Re: About instance's integrity.
  • Next by thread: Re: About instance's integrity.
  • Index(es):
    • Date
    • Thread