<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><div id="bloop_customfont" style="margin: 0px;">Hi Heiko,</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Pipeline.get(name, ..) is a method to return a PipeLoader (a Pipe wrapper using Loaders) instead a Pipe. </div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Loaders[1] were designed for activities and fragments in order to cleanly handle configuration changes that occur in Activites and Fragments. So, for service you need to use a Pipe (Pipeline.get(name)) and AbstractCallback (or Callback)</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">[1] http://developer.android.com/guide/components/loaders.html</div><div id="bloop_customfont" style="margin: 0px;"><br></div></div> <div id="bloop_sign_1395669056737899008" class="bloop_sign"><span style="font-family:helvetica,arial;font-size:13px"></span>-- <br>Daniel Passos<br><br></div> <br><p style="color:#000;">On March 24, 2014 at 4:32:57 AM, Heiko W.Rupp (<a href="mailto:hrupp@redhat.com">hrupp@redhat.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hey,
<br>
<br>[ this is with 1.3.1 ]
<br>
<br>Pipeline.get(name, ..) allows to use Fragments and Activities as "callbacks".
<br>
<br>What is the recommended way to use that inside a Service?
<br>
<br>>From looking at the code I think the logic inside LoaderAdapter
<br>could accept the AbstractCallback as sort of "fallback" for
<br>cases that are neither Activity nor Fragment.
<br>
<br> Thanks
<br> Heiko
<br></div></div></span></blockquote></body></html>