Quote:
Originally posted by bigstar
If the "reconnect to" is updated after a rename/move this problem seems to be resolved.
|
I was thinking, if a simple validation was performed when "reconnect to" was used, and when it detects that this current site was moved/renamed/deleted, wouldnt most of the problems be solved if Flash quickly added it to cache as a "Quick Connect" site, and continued as normal? Or, as you stated in your previous post, is there not enough information stored in memory to treat this new homeless site, as a "Quick Connect"?
There would be the problem with any files if they were previously que'd, but when this validation occurs, I suppose maybe you could prompt the user informing that the old que will need to be cleared, or need to manually update the que'd file's "site". I suppose that would clear up any confusion if this random limitation ever effects anyone else.
[I wasn't sure if this post of mine is what you were implying in your quote above, but I appologize if I am being redundant.]
cheers,
chip