Network.download is bringing from history ???

Solar2D Network
#1

Hi,
If I clear my sandbox and run my application, I verify if the connection to my web server is active, if it is, I then
[blockcode]
network.download( Session.Connect…Session.DBName…"/SalesMobile.txt", “GET”, LoadData, event, “SalesMobile.db”, system.DocumentsDirectory)
[/blockcode]

where Session.Connect is a HTTP address with the exact path needed. The problem is that if I do not change the filename, I appear to receive the old DB. Is their a way to make sure it always loads what is in the directory? Am I missing something? [import]uid: 97768 topic_id: 30705 reply_id: 330705[/import]

#2

I have the same problem when using network.download to get an image from the server. It doesn’t make sense that the api doesn’t purge the existing downloaded file and replace it with the new downloaded file that has the exact same name.

That’s why I’m calling network.download in the first place. It would make sense to add the purge option as a param of network.download, that way the developer could decide what functionality they want with an easy param specification.

I too would like to know how to remove the existing file when network.download is called.

Nail

[import]uid: 106779 topic_id: 30705 reply_id: 123057[/import]

#3

I have the same problem when using network.download to get an image from the server. It doesn’t make sense that the api doesn’t purge the existing downloaded file and replace it with the new downloaded file that has the exact same name.

That’s why I’m calling network.download in the first place. It would make sense to add the purge option as a param of network.download, that way the developer could decide what functionality they want with an easy param specification.

I too would like to know how to remove the existing file when network.download is called.

Nail

[import]uid: 106779 topic_id: 30705 reply_id: 123057[/import]

#4

We’ve used a fake “?timestamp=” appendage to the urls we’re requesting to ensure that caching doesn’t snag us. [import]uid: 117383 topic_id: 30705 reply_id: 124910[/import]

#5

We’ve used a fake “?timestamp=” appendage to the urls we’re requesting to ensure that caching doesn’t snag us. [import]uid: 117383 topic_id: 30705 reply_id: 124910[/import]

#6

Hi Kimberly, Can you please show an example using this appendage. Thanks. [import]uid: 34105 topic_id: 30705 reply_id: 126812[/import]

#7

Hi Kimberly, Can you please show an example using this appendage. Thanks. [import]uid: 34105 topic_id: 30705 reply_id: 126812[/import]