RE: [mylyn-integrators] AbstractTask vs. RepositoryTaskData inaconnector

["Tom Bryan (tombry)" <tombry@xxxxxxxxx>]

Steffen Pingel wrote on Thursday, May 15, 2008 4:33 AM:

> It is desirable to keep the number of attributes on the task class to
> a minimum. Only information that is needed for decoration, sorting,
> grouping etc. in the task list should be available from that object.
> If additional information is needed, e.g. to display incoming changes
> in the task list tooltip, the tasks framework will load the full task
> data on-demand for a task from the offline storage. This is
> reasonably fast but does not scale to a large number of tasks.

Excellent.  It took me quite some time to grasp what Mylyn was really
doing here.  Thanks also for the sequence diagram.  I am already
returning the lightweight tasks from the query.

> Yes, that is the idea. The task data is the full set of attributes
> that is loaded on-demand.

Good to know that I was on the right track.

> > > For now, I decided to stuff all of the attributes in MyTrackerTask
> > > (extends AbstractTask) because I'm also using that class to
> > > shuttle data from my service client to the RepositoryTaskData
> > > instance.  After I have all of that actually working, I figured
> > > that I could go back and make the Task List representation for my
> > > class smaller/lighter. 
> 
> I have attached a simplified sequence diagram to clarify the
> synchronization process. It shows how query results are processed in
> Mylyn 3.0: The tasks framework receives TaskData objects from the
> connector. The tasks framework then determines if the task in the
> task list needs updating and updates the offline store, task state
> etc. if that is the case. 

Thanks.  Based on some of your previous messages, I had already changed
MyTrackerTask so that it has minimal attributes (key, summary, etc.).
That seems to be working fine.

-- 
Tom Bryan <tombry@xxxxxxxxx>
Software Engineering Solutions (SES)
Cisco Systems
RTP, NC, USA