[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [prov] Download manager support for pack200


I was thinking a new separate classloader containing just the Pack200 classes.  We would still want to delegate to the bootclassloader for everything else.  However, I doubt the Pack200 classes are by themselves in their own jar that we could just create a URLClassloader for.

This was really just an idea and I haven't really thought very hard about the details :)

-Andrew



Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

01/25/2008 11:54 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] [prov] Download manager support for pack200





If the Pack200 class is loaded from the VM then it will fall under the boot class loader. There is no way we can throw that class loader away. Are you suggesting that we could somehow load this class from an isolated class loader that is not connected to the boot class loader?

Tom



Inactive hide details for Andrew Niefer ---01/25/2008 09:57:39 AM---As Pascal mentioned, when we first started experimenting wiAndrew Niefer ---01/25/2008 09:57:39 AM---As Pascal mentioned, when we first started experimenting with Pack200 we had memory problems. It seemed that Pack200's interna

From:

Andrew Niefer <aniefer@xxxxxxxxxx>

To:

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Date:

01/25/2008 09:57 AM

Subject:

Re: [equinox-dev] [prov] Download manager support for pack200






As Pascal mentioned, when we first started experimenting with Pack200 we had memory problems. It seemed that Pack200's internal data was static and not cleared between each jar that was packed. So once we had packed a reasonable number of jars we started running out of memory.


It could be that we had been doing something wrong. It is also possible that we could work around this by playing with class loaders (under the assumption that if the classloader was garbage collected, all that static memory would go away).


-Andrew


Thomas Hallgren <thomas@xxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

01/25/2008 02:53 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] [prov] Download manager support for pack200







Just out of curiosity, why do you use the external binary to do the
pack/unpack and not the java.util.jar.Pack200 class? It seems to me that
a fragment that is EE dependent (require Java 1.5 or higher) would be
ideal here. Those who run lower then Java 5 simply would not have
pack200 which is kind of natural isn't it?

- thomas

Jeff McAffer wrote:
> right but there is the practical detail that the exe you need comes
> with Java 5 or later and the licensing does not likely allow you to
> ship just the unpack200 exe.  But that is a matter for someone's legal
> team.  As John says, the unpack support simply cares whether or not
> the exe is there.
> What we really need is an open source implementation of unpack that
> runs on/with Foundation...
>
> Jeff
>
>
> John Arthorne wrote:
>>
>> Just to clarify, the JRE level doesn't matter here. Unpack is
>> performed by a standalone unpack200 executable that doesn't require
>> presence of a JVM.  You can run with a Foundation class library, plus
>> a standalone unpack200 executable from Java 5 or Java 6.
>>
>>
>>
>> *Jim Colson <jccolson@xxxxxxxxxx>*
>> Sent by: equinox-dev-bounces@xxxxxxxxxxx
>>
>> 01/24/2008 09:18 PM
>> Please respond to
>> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>>
>>
>>    
>> To
>>     Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>> cc
>>     Equinox development mailing list <equinox-dev@xxxxxxxxxxx>,
>> equinox-dev-bounces@xxxxxxxxxxx
>> Subject
>>     Re: [equinox-dev] [prov] Download manager support for pack200
>>
>>
>>
>>    
>>
>>
>>
>>
>>
>> how would that work on J2ME (CDC/Foundatoin)?
>>
>>
>> ________________________________________
>> Jim Colson, Chief Architect - IBM Client Software
>> Distinguished Engineer
>> IBM Academy of Technology
>> Board Member - IT Architect Certification
>>
>> 11501 Burnet Rd. Austin, TX 78758
>> Ph 512-823-7357, Fax 512-838-0962
>> email: jccolson@xxxxxxxxxx
>>
>> Admin:  Sandra Wallis 512-838-3241
>> email:  swallis@xxxxxxxxxx
>>
>>
>>
>>                                                                      
>>                                                     From:      
>> Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>          
>>                                                    
>>                                                                      
>>                                                     To:        
>> Equinox development mailing list
>> <equinox-dev@xxxxxxxxxxx>                                            
>>      
>>                                                                      
>>                                                     Date:      
>> 01/24/2008 08:11 PM                                      
>>                                                    
>>                                                                      
>>                                                     Subject:    
>> [equinox-dev] [prov] Download manager support for pack200
>>                                                    
>>                                                                      
>>                                                  
>>
>>
>>
>>
>>
>> I seem to remember that someone was working on adding to support to our
>> download manager to favor downloading pack200'ed artifacts over
>> canonical
>> ones.
>> Did that ever made it into the code?
>>
>> Thx
>>
>> PaScaL
>>
>> _______________________________________________
>> equinox-dev mailing list
>> equinox-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/equinox-dev
>>
>>
>> _______________________________________________
>> equinox-dev mailing list
>> equinox-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/equinox-dev
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> equinox-dev mailing list
>> equinox-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/equinox-dev
>>  
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx

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

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