java - Android SignalR should be implemented as Service or IntentService? -


on android app, i'm implementing signalr connection (https://github.com/erizet/signala) connect hub server send requests , receive responses.

a sample of code follows:

signalaconnection = new com.zsoft.signala.connection(constants.gethuburl(), this, new longpollingtransport()) {     @override     public void onerror(exception exception)     {     }      @override     public void onmessage(string message)     {     }      @override     public void onstatechanged(statebase oldstate, statebase newstate)     {     } };  if (signalaconnection != null)     signalaconnection.start();

there's sending bit

signalaconnection.send(hubmessagejson, new sendcallback() {     public void onerror(exception ex)     {     }      public void onsent(charsequence message)     {     } });

the sending , receiving occur across activites, , responses sent @ random times regardless of activity, also, connection should opened long app running (even if app running in background) that's why wish implement signala connection background service

the question should implement as:

1 - service (http://developer.android.com/reference/android/app/service.html)

or

2 - intent service (http://developer.android.com/training/run-background-service/create-service.html)

keeping in mind need send strings service , response strings service.

i grateful if show me how implement kind of connection in code background service/intentservice.

thanks reading.

update:

please see demo activity made developer how implemented signala https://github.com/erizet/signala/blob/master/demo/src/com/zsoft/signalademo/demoactivity.java

the problem aquery (which know nothing about) being used in demo activity. aquery run in background time ? problem is, latest update on signala mentions following

i have changed transport. longpolling uses basic-http-client instead of aquery http communication. i've removed dependencies on aquery.

hence i'm not sure whether should follow demo activity or not

update 2:

this thing confusing me in intentservice, onhandleintent method calls stopself after finishes tasks, when want code in intentservice keep running time

protected abstract void onhandleintent (intent intent) added in api level 3 method invoked on worker thread request process. 1 intent processed @ time, processing happens on worker thread runs independently other application logic. so, if code takes long time, hold other requests same intentservice, not hold else. when requests have been handled, intentservice stops itself, should not call stopself().

signala running on thread creates , starts connection, network access done in background. remaining work on starting thread lightweight, hence ok on ui tread.

to answer question, need have thread running signala connection. therefore think service best choice since signala need running time.

regarding aquery , demo project. removed dependencies aquery in libraries, not in demo. clear, don't need aquery run signala.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more