Hello, all!
This a follow-up to a thread started last July. I looked into a lot of things,
tested some crazy ideas (that went wrong) and came to my final decision for my
project. I consider it very important to let people know what I decided. Maybe
I can help someone. And, for sure, you guys c
On Mon, Oct 8, 2012, at 08:40 AM, Flavio Donadio wrote:
> Hello, all!
>
>
> This a follow-up to a thread started last July. I looked into a lot of
> things, tested some crazy ideas (that went wrong) and came to my final
> decision for my project. I consider it very important to let people know
>
Kyle,
I like your points and I considered them. It's been 3 months of hair-pulling
and I still have some uncertainty about my choices. But I think I made the best
decisions, and here's why...
> We still run WO 4.5 to power our own store, but we go through some major
> hoops to do so.
>
> Pers
Thank you Flavio. Out of curiosity, did you encounter pessimistic vs.
optimistic locking performance/data reliability issue in having many clients
writing to potentially the same places at once? If so, how did each of the
candidate solutions answer the problem that this poses?
The problem be
On Oct 9, 2012, at 1:00 AM, Simone Tellini wrote:
>
> this is way overkill. You can simply write a simple utility to dump the
> content of your resource in a C file:
>
> static char foo[] = {
>0x01, 0x02, 0x03,
> ...
> };
>
> You don't need to use assembly nor to create bogus functio
On 07.10.2012, at 22:04, Andrew Madsen wrote:
> The problem is that if I include a 1024x1024 icon ("icon_512x...@2x.png"),
> the icon does not display on 10.5. Finder doesn't display the icon, and when
> it is opened in Icon Composer on 10.5, it appears to be blank/empty. If I
> remove this lar
On 08/10/2012, at 17:56, Alex Zavatone wrote:
> Thank you Flavio. Out of curiosity, did you encounter pessimistic vs.
> optimistic locking performance/data reliability issue in having many clients
> writing to potentially the same places at once? If so, how did each of the
> candidate solutio
Il giorno 09/ott/2012, alle ore 03:15, Alexander Bokovikov
ha scritto:
>
> On Oct 9, 2012, at 1:00 AM, Simone Tellini wrote:
>
>>
>> this is way overkill. You can simply write a simple utility to dump the
>> content of your resource in a C file:
>>
>> static char foo[] = {
>> 0x01, 0
