This one time, at band camp, Thomas Yip said:
I agree with most of the discussion about the status of Castor JDO
being stagnant for a while now.
As for on-going development, most of us have just been dealing with
life. Personally, over the last year I've been laid off twice from
the dot com bust. Let me tell you, job hunting in this economy
require a *lot* of time and effort. I know that others have been
affected by similar situations. For example, Thomas was taken off
of full-time Castor development due to the restructuring at Intalio.
I'm not trying to make excuses, I'm simply trying to offer the
lurkers on the list a small picture into other aspects of our lives
that have had a deep impact on the project.
I completely agree that we need a strategy moving forward so that
JDO can begin to gain the momentum it once had. The following list
posted by Thomas seems to be a starting point. Let's all try to
remain professional and refocus the effort being used in this thread
to move forward and get Castor JDO rolling again.
TY>Whatever performance concern is big issue depending on how
TY>a user use Castor. I can remember 10 more features that users claim
TY>they will abandon Castor if it is not implemented right the way.
TY>1/ Uni-directional relationship support
TY>2/ Polymorphism collection
TY>3/ Foreign key as part of primary key
TY>4/ Long transaction without depending on cache
TY>5/ Cache purging
TY>6/ Solve 4K BLOL limitations
TY>7/ Distributed cache
TY>8/ Self reference relationship (object link to objects of the same type)
TY>9/ Loading without extensive SQL join (*the* performance limitation)
TY>10/ Relationship with attribute
TY>11/ Cascade delete of "independent" object
TY>12/ OQL Enhancements
TY>13/ QueryResult got garbage collected
OK, let's get down to brass tacks. Is there any significance to the
order of this list? I'm not seeing all this stuff in Bugzilla. Let's
get this stuff in Bugzilla (even if they are just requested
enhancements). That will allow us to track them and also post our
own notes. It will also allow a full description of the problem and
how to reproduce it. (I know that I"ve spent hours trying to reproduce
a defect with no success - that is damn frustrating!)
I know that the 4K BLOB limit usually surfaces with Oracle. This
limit is imposed by Oracle's thin driver. I've personally used the
Oracle OCI driver to eliminate this problem in the past. I do not
have any knowledge of BLOBs with other databases.
Some of the items in this list will require a very large amount of
work. I think we really need a priority so that we can begin working
on them.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
