Yes, as I mentioned in yesterday's call, I am working on structuring the 
xml writers and handlers so they can be used at finer than  repository/etc 
granularity.  As always, there are trade-offs to make about the 
simplicity/complexity of the data and of the writing/parsing and blind 
versus intelligent reuse, but at least we should have the mechanisms 
available to allow us to make the right choices.

        - Dave




Stefan Liebig <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
10/23/2007 12:38 AM
Please respond to
Equinox development mailing list <[email protected]>


To
Equinox development mailing list <[email protected]>
cc

Subject
Re: [equinox-dev] De/Serializing IArtifactKey






Yes!

Maybe there is something reusable from the xstream eliminating work.

Stefan

Jeff McAffer wrote: 

So far the approach has been that ArtifactRepositories and/or processing 
steps are responsible for defining how descriptors are written.  So, in 
the delta case, the need to serialize an ArtifactKey is driven by the 
implementation of the delta processing step.  You should therefor store 
the needed information any way you want.  Of course, if it turns out that 
alot of people need to serialize some object then it would be convenient 
to have this code written once and shared.  For now I suggest you just do 
whatever works best for (i.e., put it in your bundle and make it work 
however is best for you) and we can look at consolidation later if needed. 


Make sense? 

Jeff 



Stefan Liebig <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED] 
10/22/2007 09:41 AM 

Please respond to
Equinox development mailing list <[email protected]>



To
Equinox development mailing list <[email protected]> 
cc

Subject
[equinox-dev] De/Serializing IArtifactKey








For the delta processing steps I need to ´store´ an IArtifactKey into a 
string. This artifact key identifies the predecessor used for 
patching/diffing.
I created a simple class performing this serialization and 
de-serialization (comma separated list of the properties of IArtifactKey).
What is better?
- Split this De/Serializer class and place the Serializer and the 
De-serializer where they are used
- Keep it together (one class) and place in the package 
org.eclipse.equinox.p2.metadata
- ..

Stefan
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev



_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
 
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to