Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [osee-dev] Relation Ordering Changes 
We can change that since this is the main data structure used to
transfer data between the client and server.  

-----Original Message-----
From: Finkbeiner, Andrew M 
Sent: Wednesday, August 12, 2009 10:29 AM
To: OSEE Developers mailing list
Subject: RE: [osee-dev] Relation Ordering Changes

I'd like to reuse that code, especially the xml writing portion, but I'm
a bit concerned that it's using Dom xml parsing instead of sax.  This is
code that will run often, so it will likely be a significant impact.
Thoughts?

-----Original Message-----
From: Escobar, Roberto E
Sent: Wednesday, August 12, 2009 10:04 AM
To: OSEE Developers mailing list
Subject: RE: [osee-dev] Relation Ordering Changes

Andy, 

For the xml portion, you may want to use the PropertyStore object since
it already provides a mechanism for storing data to xml format. 
See the User Settings attribute in the UserArtifact class. 


-----Original Message-----
From: Finkbeiner, Andrew M
Sent: Tuesday, August 11, 2009 1:43 PM
To: osee-dev@xxxxxxxxxxx
Subject: [osee-dev] Relation Ordering Changes

A fully robust relation ordering solution needs to handle conflict
detection, concurrent modification, performance considerations, and an
API that supports graphical and non graphical use-cases.  Here is a
summary of what has been discussed thus far.

We have identified 3 basics types of ordering; user-defined,
lexicographical order, and unordered.  Each relation type will have a
default order type associated with it.  If someone wants to specify a
sort order other than the default, or the type requires meta-information
such as user defined, then that information will be stored in an
attribute on the parent artifact.

The attribute with the order information will be an xml string and there
will be a maximum of one orderAttribute per artifact.  This means that
multiple relationType to orderType pairs may be in the attribute.

Example xml:
<OrderList>
<Order relationType="name" orderType="someGuid"
list="guid1,guid2,guid3"/>
<Order relationType="name2" orderType="someGuid"
list="guid3,guid2,guid1"/>
</OrderList>

Thoughts, concerns, etc..?

-Andy
_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev
_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev
_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev

Back to the top