Only theoretical speaking: what makes that limit? Is it real with Mac OS 9? Can we use 2 or more resourceforks with interapplication calls?
the resourcemanager is what makes the technical limit for the max. size allowed for resourceforks.
the technical details are unknown terrain for me.
and while i am aware that it is a bullshit project (because files with a bigger resource forks wouldnt work on other systems) but i am somehow curious if you could break the limits - among other things, this could explain why the limit once was made.
Can we use 2 or more resourceforks with interapplication calls?
yes, exactly, if you needed more you could just use additional files.
there is one classic example where this has been done that way: in cubase 5.x most of the resources went to a "cubase resources" document, probably because they were afraid that the images could get too big.
and I am interested in how you notice that limit?
i read about it when i was searching something about the HFS+ API, which is completely unreleated.
the custom files i create with my apps are usually data fork only.
the only example of a resourcefork where you theoretically want to have unlimited space is the window monkey controlpanel; if you add images to it, they end up in a resource fork. 16 mebibyte are enough for some 10,000 images though, so its really only theoretical.