Jump to content

Syncing image files


rainman
 Share

This topic is 2797 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

We currently do extensive home inspections on the ipad with about 100 images, mostly medium sized photos that I want to sync back to the main database. What is your experience iwth image synching? Other prodcuts take way to long to sync.

Link to comment
Share on other sites

I don't think it matters how you store the image (on the host). Moving images is slow. Base64 encoding, as we use for EasySync, does not support Secure External storage.

Link to comment
Share on other sites

What file size will the images be on average?

When syncing, will users be using cellular data (LTE / 4G / 3G?), wifi over a WAN (what speed?), or wifi on the LAN?

Barbara, I'm not sure why you say that external secure storage cannot be used with base 64 encoding - why wouldn't that work? If it gets put into a container field on the server, wouldn't it just use whatever setting the server is configured with?

Link to comment
Share on other sites

Jesse, From Tims troubleshooting page for EasySync:

Some synced containers are being corrupted. Why?

One possible explanation is that the values in the containers are being stored using FileMaker's "compress" option. There is a known issue with FileMaker's Base64 encoding function, where the function does not first decompress a container's contents prior to encoding. To avoid this problem, do not use compressed containers.

Note: This issue also applies to secure, external containers. FileMaker is not decrypting the containers before Base64 encoding them. As a result, decoding those values returns incorrect values.

And this thread : http://fmforums.com/forum/topic/94723-container-fields/

Link to comment
Share on other sites

Hi Barbara - I did see the problem you're talking about when using compressed files, but I did not see the problem with secure external storage (unless they happened to also be compressed).

 

In MirrorSync, you can set the $$base64Limit global variable to zero to force MirrorSync to transfer container data as a guest of FileMaker server instead of using Base64. That solves the problem of syncing compressed files.

Link to comment
Share on other sites

@rainman - I'm still waiting for an answer on the questions I sent you. If you can give me some answers on those, I'll try to set up some testing benchmarks here to give you an idea of what to expect for sync performance.

Link to comment
Share on other sites

This topic is 2797 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.