search

joelmap / geohashdroid

Automatically exported from code.google.com/p/geohashdroid
0 stars 0 forks source link

store wiki messages when connection is down #23

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If the connection times out, or no uplink is available, messages and photos 
should be 
stored with timestamp and location that on the phone. They should be 
synchronized either 
with the next message sent, or by manual trigger.

This would allow to bridge reception holes, or to keep messaging as usual and 
to upload 
the full report at home (might also be useful for people without data tariff, 
but with wifi)

In the latter case, the app should probably be able to store messages for 
several 
expeditions (graticule-date combinations) until an uplink is reached.

Original issue reported on code.google.com by thomas.h...@gmail.com on 13 May 2010 at 5:50

GoogleCodeExporter commented 9 years ago 
Hm.  That sounds like a good idea, actually.  And this may be something that 
the 
background service I made (in the 0.8.0 prereleases or in the SVN trunk) could 
be 
extended to include.  That is to say, any time a message or photo is to be 
sent, it 
just gets queued up with the service.  If it fails to send it due to connection 
timeouts or unavailable data connections, it could wait a few seconds and try 
again, 
or just wait until a data connection comes up (either WiFi, 3G, or whatever) 
and keep 
going through the queue.

Or, maybe I could just make a separate dedicated service for that.  But yeah, I 
can 
see this working out in time.

Of course, we'd also need some GUI interface to handle failures in that case 
(i.e. 
"abort all queued entries", "change username and password and try again", etc), 
but 
that could be dealt with, too.

Original comment by captains...@gmail.com on 13 May 2010 at 7:39

GoogleCodeExporter commented 9 years ago 
Oh, hey, I'm still working on this.  I don't have anything working yet, but 
I've got a lot of the backend required for this in the queueservice branch.  
I'm trying to make it push all uploads off to the background, where it'll keep 
trying until it either posts or runs into an error that can't be solved by an 
internet connection (bad password, wiki returns invalid data, etc).  So I 
haven't forgotten about this suggestion. :-)

Original comment by captains...@gmail.com on 20 Mar 2011 at 12:54