> on the client side, is there a solution that'll keep a > connection open and poll every few seconds to > find out how far along the process is. Since you perform an HTTP POST, your client just waits for the server response, in meantime from your java code point of view you can no do nothing (blocking function), it will only wake up when the full bunch of data will be available from TCP to your java applicative layer.. or if the TCP connection is reseted from one side of the connection or if it's "time out'ed". May be intermediate HTTP responses with a 100 (continue) status could suit your issue, i'm thinking of that because your could had some specific HTTP headers containing the information you want ..
Another solution would be to work at socket java level, if you want a more accurate view on what's going on in your request, but i do not even know if it could solve your issue.. Anyway, Polling a server to find out how much time a request would take, seems to me quite strange.. are you really sure you have the good approach? On Mar 4, 10:57 pm, dashman <erjdri...@gmail.com> wrote: > I'm doing a POST to a site to do some work...this process > takes a long time (about 30-60 seconds). > > I plan change it so that i can do the work in a separate > thread on the server. > > on the client side, is there a solution that'll keep a > connection open and poll every few seconds to > find out how far along the process is. > > on the UI front, is there a way to change the size of the > indeterminate wait animation - something larger. > > any any pointers how this could be handled also > appreciated. > > it's java on both the client and server. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
