software development iPad, web services and social integration
From the to-do list: iPad app
✔ Next Items to Work On - 2
(Completed by Denis Slabakov on September 10, 2012)
Comments
Sudhir Kelappan on August 10, 2012:
- on any screen, except for splash, if there is no user input for
given number of seconds (should be set by venue admin, limit for this
value should be set - 30sec min, 300 sec max, default value 60 sec),
application should go to splash screen
The application should never go to sleep!
Let
leave this value at 60 sec, I mean there will be no admin screen for
the moment. We will add this functionality in next versions.
- please check - photos upload to the server should run in separate execution thread, upload process should be FIFO
- please check - text messagees upload to the server should run in another separate thread, FIFO, as well
Sudhir Kelappan on August 10, 2012:
Sudhir Information on thread and FIFO for text message and photo message upload.
We verified and found the following: 1. The upload process is Asynchronus and it is working fine. 2. The FIFO is not enforced in code. But generally the behaviour is FIFO
Introducing
a separate execution thread may probably add complexity. But we can
think of enforcing the FIFO by doing sequential uploads.
Pls. advise how you want this to be done.
Denis
Please explain in more details how the process of photo and text upload is done.
Specifically, what would happen if there will be more that one session of photos taken, and there will be a queue.
What would happen if there will be a temporary loss of internet connection?
Sudhir Kelappan on August 13, 2012:
Denis,
In current implementation, In case of multiple photo sessions: There is one queue created per session. Within each queue the upload will be FIFO. FIFO for the queues itself (second session's queue getting processed after the first) cannot be guaranteed.
In case of temporary loss of internet: The http request(s) would terminate and if required the calling process will get a notification. This case will have to handled specifically.
To sum up, to enforce the behaviour to be strictly FIFO will not be possible with the current implementation. We will have to think of an alternate implementation.
Pls. advise. Once you let us know the exact requirement we will get back to you with the appropriate design.
Denis Slabakov on August 13, 2012:
I did not understand how the system would perform under internet connection loss, please explain in more details
Is it possible to make sure that photos from the second shooting does not start to upload until photos from first shooting has been uploaded?
Denis Slabakov on August 22, 2012:
I did not check 60 sec in every screen, but it seems to be working - done
FIFO - what is the status in this build?
Sudhir Kelappan on August 22, 2012:
The FIFO is done . We will be giving a build shortly.
There is an issue on server side which needs to be fixed. The Russian message text that is saved in database is not displaying correctly. We will be fixing this. This works fine for English text.
-Sudhir
Denis Slabakov on August 22, 2012:
unicode should fix the problem
Denis Slabakov on August 28, 2012:
is it done?
Sudhir Kelappan on August 30, 2012:
Dear Denis,
This is done from iPad side by converting the text to unicode (UTF-8) and then transmitting.
On the server side there is some issue with the MySQL database and JAVA connector that is used for it which is preventing the insertion of utf-8 russian text into the tables. http://bugs.mysql.com/bug.php?id=3114
It seems to be configuration issue and whatever needs to be done in code is already done. I am seeking expert help on this and will be freeing up the developer for other tasks.
Once the solution is available i will update you.
I have given the build for iPad that includes this change. All other functions in iPad is unchanged.
Comments
Sudhir Kelappan on August 10, 2012:
The application should never go to sleep!
Let leave this value at 60 sec, I mean there will be no admin screen for the moment. We will add this functionality in next versions.
- please check - photos upload to the server should run in separate execution thread, upload process should be FIFO
- please check - text messagees upload to the server should run in another separate thread, FIFO, as well
Sudhir Kelappan on August 10, 2012:
Information on thread and FIFO for text message and photo message upload.
We verified and found the following:
1. The upload process is Asynchronus and it is working fine.
2. The FIFO is not enforced in code. But generally the behaviour is FIFO
Introducing a separate execution thread may probably add complexity. But we can think of enforcing the FIFO by doing sequential uploads.
Pls. advise how you want this to be done.
Denis
Please explain in more details how the process of photo and text upload is done.
Specifically, what would happen if there will be more that one session of photos taken, and there will be a queue.
What would happen if there will be a temporary loss of internet connection?
Sudhir Kelappan on August 13, 2012:
Denis,
In current implementation, In case of multiple photo sessions:
There is one queue created per session. Within each queue the upload will be FIFO. FIFO for the queues itself (second session's queue getting processed after the first) cannot be guaranteed.
In case of temporary loss of internet:
The http request(s) would terminate and if required the calling process will get a notification. This case will have to handled specifically.
To sum up, to enforce the behaviour to be strictly FIFO will not be possible with the current implementation. We will have to think of an alternate implementation.
Pls. advise. Once you let us know the exact requirement we will get back to you with the appropriate design.
Denis Slabakov on August 13, 2012:
Is it possible to make sure that photos from the second shooting does not start to upload until photos from first shooting has been uploaded?
Denis Slabakov on August 22, 2012:
FIFO - what is the status in this build?
Sudhir Kelappan on August 22, 2012:
The FIFO is done . We will be giving a build shortly.
There is an issue on server side which needs to be fixed.
The Russian message text that is saved in database is not displaying correctly.
We will be fixing this.
This works fine for English text.
-Sudhir
Denis Slabakov on August 22, 2012:
Denis Slabakov on August 28, 2012:
Sudhir Kelappan on August 30, 2012:
This is done from iPad side by converting the text to unicode (UTF-8) and then transmitting.
On the server side there is some issue with the MySQL database and JAVA connector that is used for it which is preventing the insertion of utf-8 russian text into the tables.
http://bugs.mysql.com/bug.php?id=3114
It seems to be configuration issue and whatever needs to be done in code is already done.
I am seeking expert help on this and will be freeing up the developer for other tasks.
Once the solution is available i will update you.
I have given the build for iPad that includes this change. All other functions in iPad is unchanged.
-Sudhir K
Denis Slabakov on September 10, 2012:
Sudhir Kelappan on September 10, 2012:
This is Done.
-Sudhir