Umm, I must have been misunderstood.  I use Store for both Silt (my 
blog server) and BottomFeeder - see the public repository for the 
long history of both products.

I use parcels as my deployment mechanism for both Silt and 
BottomFeeder.  For the blog server, I have the application server 
load from parcels each time it starts (thus giving me a 
deterministic, reproducible startup procedure).  I use parcels to 
build the BottomFeeder application, and have parcels as the update 
mechanism - i.e., you can check for updates in the app, and it will 
download parcels and load them at runtime (and at startup the next 
time it runs).

I'm not sure where this impression comes ffrom, but it's not the case.

>At ESUG 2006 James Robertson said he doesn't use Parcels for code
>deployment because they are just not reliable (of course he doesn't
>use store either). He uses change sets (or .st files, I don't remember
>exactly) instead.
>
>Philippe
>
>> >
>> >> May be I should post to VW to see what are the problem with
>> >> deployed code in VW.
>> >> A parcel in VW has dev and depl prerequisites and it seems to work
>> >> too.
>> >
>> > Well, sure. Sorta. Kinda. :-) We can do the same in Squeak with
>> > projects and change sets and it seems to work, too. Sorta. Kinda. :-)
>>
>>rofl :-)
>>
>> >
>> > Cheers,
>> >   - Andreas
>> >
>> >
>>
>>

<Talk Small and Carry a Big Class Library>
James Robertson, Product Manager, Cincom Smalltalk
http://www.cincomsmalltalk.com/blog/blogView