Bitmessage disconnects or timeouts.

it will quit after try_factor exceeds 512, right? and that will happen
after a delay of 1+2+4+8+16+...+256+512 = 1024 seconds = 17 minutes

On Thursday, July 24, 2014, Gricha <notifications@github.com> wrote:

> In src/shared/bitmessage_communication/bitmessageserver.py:
>
> > @@ -20,12 +20,26 @@ def get_exception_number(result):
> >
> >  class BitmessageServer:
> >    def __init__(self):
> > -
> > -    self.api = xmlrpclib.ServerProxy("http://{0}:{1}@{2}:{3}".format(
> > -        BITMESSAGE_USERNAME,
> > -        BITMESSAGE_PASSWORD,
> > -        BITMESSAGE_HOST,
> > -        BITMESSAGE_PORT))
> > +    try_factor = 1
>
> Actually it won't ail after 17 minutes, it will call function again and
> try to reconnect again. And so on..
> … <#1476905798f02c73_>
> On Thursday, July 24, 2014, Tomasz Kolinko <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote: In
> src/shared/bitmessage_communication/bitmessageserver.py: > @@ -20,12 +20,26
> @@ def get_exception_number(result): > > class BitmessageServer: > def
> __init__(self): > - > - self.api = xmlrpclib.ServerProxy("http://{0}:{1}@{2}:{3}".format(
> > - BITMESSAGE_USERNAME, > - BITMESSAGE_PASSWORD, > - BITMESSAGE_HOST, > -
> BITMESSAGE_PORT)) > + try_factor = 1 try_delay instead of try_factor could
> be cleaner, but no need to change that. — Reply to this email directly or
> view it on GitHub <https://github.com/orisi/orisi/pull/75/files#r15344388>.
>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/orisi/orisi/pull/75/files#r15353680>.
>


-- 
twitter: @kolinko
phone#: +48 600 359 921
http://www.appcodes.com/
http://www.appmentionalerts.com/