With apologies for the cross-posting, but I wasn't sure which of these
three
groups would be best placed to answer my peculiar question.
My company is redeveloping a syndication system which sends pictures from
our premises securely across the Internet and onto servers at our
customers'
sites. In the old system, at the customer site we had our own hardware box
running a UNIX variant. We had a matching UNIX box at our site. Both UNIX
boxes were running 'netatalk'. This meant that we could use Adobe
Photoshop
on the Mac to save pictures onto a Mac-ex****ted volume from the server,
transfer the two UNIX files (the JPEG, and it's "AppleDouble" file) to the
customers' server, put the two files back in the right place and presto,
the
picture is available to remote Macs complete with its custom icon and all
of
the other goodies that Photoshop puts in the resource fork.
Now, we want to change the system so that we don't have hardware at the
other end - we give them software and they install it on their own
machines.
If they are running UNIX, fine - but we expect many of them to be running
Windows, and yet still want pictures shared to their Mac networks, with
custom icons and the other resources and Finder Info intact.
I know that Windows servers can ex****t suitable Mac volumes. What I
*don't*
know is how to "fake" the resource fork [and Finder Info] in place, from a
PC application developer's point of view. I know how to construct the
binary
file, I just don't know where to put it [no sniggering at the back].
Any help that you can provide would be greatly appreciated.
Paul
|
