> It is ok to have Peer stuff outside of om, but in this case,
> it probably should be moved into there.
Ok, where should it go? I think it could be moved under
om/schedule/JobEntry.java and om/schedule/peer/JobEntryPeer.java
(which means creating a new directory, om/schedule).
How about the other files in services/schedule that are not
specifically a service implementation? (I'm referring to
JobQueue.java and WorkerThread.java). Should these be also
moved to om/schedule, or should they be left alone?
What is, in general, the criteria for this? I can see how a
Peer class and its associated "functionality" class could
be said to belong in om/, but directories such as om/security
and om/user do have other stuff in them...
One more thing: is Jon's opinion enough of a "do it", or should
I wait for more opinions and an agreement to be reached?
> -jon
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
