Hi everyone, We know this Google outage is a major problem for many of our customers, but this is not caused by Spanning Sync. The last response from Google in the thread linked to by Charlie was for us to send some reports of the outage so they can try to figure out what's causing the problem. We've done this many times and will continue to provide Google with reports to assist in finding the issue. We're hopeful this will be resolved soon.
There is no simple work-around that we can implement in Spanning Sync to circumvent this problem. Spanning Sync communicates with Google through Google's Client URL, which is where the issue is coming from. Changing Spanning Sync to communicate with Google through something other than the Client URL (if there is one), would require a complete re-write of Spanning Sync from the ground up. That's a complete overhaul/re-write and not a simple work-around. This would also require many many months of coding to accomplish this. That's not very feasible considering Google is working on the problem and it could be fixed any time now. As I stated above, we know this is a major problem and very frustrating, but we're doing everything we can to assist Google in finding the problem. In the end, it's Google's problem to fix and we're hopeful they will do so in a timely manner. Please be patient and trust that we're actively doing everything possible to get this resolved. Thanks, Byron --- Byron Shaheen [email protected] http://spanningsync.com On Jun 28, 9:05 am, thewgp <[email protected]> wrote: > What other solutions are you guys using? I'm about to give up on > Spanning Sync because of this and ask for a refund. > > Unfortunate that it's happened this way, but there hasn't even been > any update to the Google discussion for this problem since June 10 - > and that discussion seems to indicate the Spanning Sync devs are > having issues communicating with Google. The last post was from a > USER pleading for some relief, and there was no reply. Given that, > I'm not sure Spanning Sync has a very high likelihood of any sort of > workaround, or that Google has any sort of fix coming in the near > future. > > Devs: It's been nearly a month now - should you not be considering > alternative strategies? Apparently there are other sync programs that > do NOT have this issue so other methods clearly exist. I appreciate > your posting to let everyone know it's Google's problem, and I can > appreciate that - but it doesn't look like Google is going to fix it, > so either you need to implement a workaround or take steps to > discontinue Spanning Sync, at least in its current form. > > Nothing personal - I'm just saying what many are thinking. -- You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en.
