[Dev] parcel modularity... not

[Kapil Thangavelu]

hi katie,

On Fri, 2004-08-27 at 19:27, Katie Capps Parlante wrote:
> Hi Kapil,
> 
> You've brought up several issues, including:
> 
> + logging system
> + how to extend the chandler ui with parcels
> + overall ownership issues
> + likelihood of a patch getting accepted if it spans owners
> 

several more. 

unifying networking approaches to using twisted, the dav/sharing stuff
is all using synchronous networking at the moment from the gui thread.

general consensus and recommendations on a standard parcel layout. of
course thats predicate on the term parcel having some meaning, as a
modular unit, which the currently doesn't hold true, as parcels are
being used/abused for framework registration units with lots of implicit
interdependencies. such that scattered parcels are used to form a
semantic modular unit. having any working documentation on how to make a
parcel would go a long way towards answering this, and having those
standards followed by osaf parcels would be helpful as well.

parcel lifecycle, some parcels end up performing operations which its
impossible to disable, zaobao for example starts up a background check
pulling in rss stuff. how do i disable zaobao. or say i install morgen's
very cool web server stuff, how do i disable it. currently the only
answer is remove it, but then my repository is hosed if it tries to load
some of the content items from these parcels, say for example via
following a reference. thats great for now when the answer is to blow
away the repository, but for the future, it begs for infrastructure to
manage parcels. ie something akin to enabled flag for parcels, with a
corresponding invocation to onShutdownDown (parallel to onStartupUp) or
onPause/onDisable. taking a step further it could be generalized to a
different form of disconnected operation, but thats out of scope for the
moment. all though it does put me in mind of an issue i raised on irc a
few months ago, namely chandler could really use a component/adapter
architecture. the discussion in the thread for emailaddresses is a
timely and relevant example, for factory components. 

> I'm the overall owner of engineering issues not being handled by anyone 
> else, and the first two items you mentioned are on my radar. That said, 
> I haven't had a lot of time to spend on this for various reasons. If you 
> would like to help us solve some of these problems, I suggest you write 
> up a proposal and send it to the dev list for feedback. If you create a 
> proposal and build some consensus around it, I will take responsibility 
> for making sure a decision gets made and any relevant patches applied.
> 

i'll work on a logging proposal.

cheers,

-- 
Kapil Thangavelu <hazmat at objectrealms.net>       Vision Implemented
objectrealms.net <http://www.objectrealms.net>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20040827/3ebc0d48/attachment.bin