HTTPService not reading updated xml, i've been having torefresh the xml in my browser manually

[LittleMuscle]

I am calling an HTTPService (id=data2php) which runs a php script which creates
an xml doc and puts it on my server. i then call another HTTPService
(id=feedRequest) which reads the xml doc. i then try to populate a datagrid
with the lastResult of my HTTPService that reads the xml doc. My issue is that
that the HTTPService which reads the xml doc reads the previous incarnation of
the xml doc, not the newly created one that my HTTPService (data2php) created.
i've been manually going to the xml doc in my browser and hitting refresh for
my feedRequest HTTPService to read the updated xml.

here is the mxml for the httpservice that reads the xml:
<mx:HTTPService id="feedRequest"
url="http://cfcdi.org/eric/dashboard/php/sales.xml" result="feedResult(event)"
resultFormat="xml" useProxy="false"/>

pretty straight forward.

(actually, once in a while it will read the updated one)

[justria]

Hm, I don't see any reasons, which it should not return correct results.

I do similar stuff in a component too an the server-side part gets updates on
each reqeust.

I suppose, you need to post more details, so that we may help further.

[jinx82002]

LittleMuscle,
Instead of binding to the lastResult property, I would explicitly handle the
result and fault events of the HTTPService (the one that reads the newly
created xml doc) and then manually update an XMLListCollection for use as the
datagrid's dp. That way, you can at least walk through the debugger and see
what's going on, and force the second HTTPService to read only when you're sure
the newly created doc is ready.

Since you said it works sometimes and not other times, it sounds like it's
just a timing problem, sometimes the xml doc is created quickly enough that the
HTTPService grabs the new xml doc, but if not, it's grabbing the old one. That
would be my guess.

[ab1301]

I had a similar problem a while back. I never really found out what was
causing the problem, but basically what was happening was that after the
httpservice got one result, it would no longer function, regardless of anything
I did to tell it to send again. The only thing that got it to work was
changing the method to post, and adding a dummy post variable.

Also, if the problem is the timing issue jinx is talking about, you might
think about eliminating the feedRequest, and having the php script called by
the data2php HTTPService return the xml file itself.

[ChrisBAH1008]

Yes, I experienced the same problem.

Despite many suggestions about invalidating data, resetting the data provider,
and so forth - the only - and I mean only - solution that worked was to send
not only a "dummy" variable into each HTTP Service URL but to make sure that
"dummy" variable was different between calls.

Therefore, I get a new Date() object in milisecond format and send this into
each of my URL data calls.

Does the trick.

[LittleMuscle]

dummy variable like this???

<mx:HTTPService id="feedRequest"
url="{'http://cfcdi.org/eric/dashboard/php/sales.xml?id='+Math.random()}"
useProxy="false"/>

or this

<mx:HTTPService id="feedRequest"
url="{'http://cfcdi.org/eric/dashboard/php/sales.xml?id='+Math.random()}"
method="POST" useProxy="false"/>

?

[ab1301]

No. Dummy variable like this:

<mx:HTTPService id="userRequest" url="http://whatever.php" useProxy="false"
method="POST">
<mx:request xmlns=""> <dummyvariable>dummyvariable</dummyvariable>
</mx:request>
</mx:HTTPService>

[ChrisBAH1008]

You can do it either way, Muscle.

[CHAOS'|nc.]

Both should work, however if you are getting timeouts instead of error I think you should go with ab's one as it limits the connection and retrieves it at the same time.

[Khanh Tran]

No. Dummy variable like this:

<mx:HTTPService id="userRequest" url="http://whatever.php" useProxy="false"
method="POST">
<mx:request xmlns=""> <dummyvariable>dummyvariable</dummyvariable>
</mx:request>
</mx:HTTPService>

THANKS SO MUCH abc1301. IT WORKS!!!