On Thursday 06 December 2007, Michael Vincent van Rantwijk, MultiZilla wrote: > > One of the bugs I'm working on now tracks what applications a project > > works with. > > Eh, how should this work? And with 'applications' you refer to: > Flock, Mozilla Firefox, Netscape, SeaMonkey, XULRunner etc, right?
These applications, yes. A project owner would have to choose which applications their project supports. > > An upcoming bug will verify an uploaded file with a hash (md5/sha1) so we > > can create InstallTrigger() links and install extensions securely. > > Dynamically (for each time InstallTrigger is called) or after the CVS > commit? The hash will be verified by the project owner and then be available for use in the InstallTrigger link. > You are aware that updates.rdf can contain many different hash codes > (one for each supported application/platform)? I'm not sure if you're talking about the applications the project supports, or that a project can have multiple types of hosted files (extensions, themes, etc). If the feed is capable of identifying multiple applications (firefox, seamonkey, etc) AND multiple files (an extension, a theme, etc) then there may be some more things for me to think about. This might not be something that more advanced projects use right off the bat (I'm just brainstorming right now anyway) - I'm just thinking that we might be gathering enough information anyway that the next logical step would be for us to create an updates.rdf feed for projects - even if it's only for the simple ones at first. -Doug
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
