askoh,
We need to start with what happens when you do choose to publish binary.
When you publish, all changes (adds, modifications and removals) are published to the repository. When you publish binary, a parcel (a .pst file and a .pcl file) is additionally published to the repository, and associated with the version of the package being published.
Every time a package is published binary, a new pair of these files is published. When you later load that version, instead of just the changes being loaded, the whole parcel file(s) are brought across the wire and "parcel loaded". Furthermore, the source pointers point to the .pst file that was brought across and put in a special directory named after the repository name id, unlike regular loading which loads the source into the .cha file.
The case for binary loading has diminished over the years as the various loaders have become more sophisticated. For instance, it used to be that code that added or modified parsing classes could only be loaded binary, whereas the analysis loader can now handle most of these cases. An example that still exists is AT Parser Compiler, which if published in a repository won't load if it is not published binary because it adds a parser as well as expects the parser to parse code in the same load. If the parser and the parse use were broken into two different packages one dependent on the other, the atomic and analysis loaders could detect and load them without the need of binary loading.
Also note that there is technically no such thing as publishing a bundle binary, only publishing each/all contained packages binary.
Finally, since publishing binary adds full .pst and .pcl files to the publish (as BinaryBlob and ParcelRecord objects) each subsequent publish is a great deal more than triple the amount of space in the repository.
IMO, the best practice is to only use it if you need it.
> What are the pros and cons for publishing binary or not in Store?
> What is the best practice?
>
> Thanks,
> Aik-Siong Koh
And So It Goes
Sames
______________________________________________________________________
Samuel S. Shuster [|]
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
