Hey Douglas--

Did you get this worked out? If not, can you provide links where I can
actually see the map in action and look at the NET requests?

Thanks! - pamela

On Thu, Sep 18, 2008 at 7:54 AM, Douglas <[EMAIL PROTECTED]> wrote:
>
> No-one interested in taking this on?
>
> Please, I really need some help on this...
>
> On Sep 17, 1:42 pm, Douglas wrote:
>> I have created an expandable banner ad for a client which uses the
>> googlemaps Flash API.
>>
>> The ad works correctly when tested locally and when tested on a
>> standard web server.
>>
>> For the web server, I generate an API key based on the domain the SWF
>> is hosted on and it works perfectly.
>>
>> The ad is going to be served through Eyeblaster. When the ad is
>> uploaded to the Eyeblaster server I use the following code to extract
>> the URL of the SWF:
>>
>> var curSwfUrl:String =  loaderInfo.url;
>>
>> I display curSwfUrl in a text field and it gives me the following:
>>
>> http://ds.serving-sys.com/BurstingRes/Site-2940/Type-2/7E415A75-380A-...
>>
>> I then generate a key using any of the following URLs and re-upload
>> the file to the Eyeblaster server but none of them work:
>>
>> http://ds.serving-sys.com/
>> orhttp://ds.serving-sys.com/BurstingRes/
>> orhttp://ds.serving-sys.com/BurstingRes/Site-2940/
>>
>> The MAP_READY event is never triggered.
>>
>> As additional information, the URL of the page in which the SWF is
>> embedded is on a different 
>> domain:http://www.eyeblasterwiz.com/admin/Tools/FlashTest/safariFrame.asp?st...
>>
>> Can anyone shed any light on why this may be happening? I will be
>> immensely grateful...
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API For Flash" 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/google-maps-api-for-flash?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to