Changes between Initial Version and Version 1 of Ticket #1556


Ignore:
Timestamp:
May 3, 2015 2:12:20 AM (6 years ago)
Author:
str4d
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1556 – Description

    initial v1  
    1 We already have a client library for apps that want to use the Java I2P APIs, and it can be used with either a remote router via I2CP, or I2P Android via a DomainSocket (which the client library handles). But there is a third option: bundle a router and use that. Bote currently bundles router.jar itself; it's not hard to do, but it isn't dead simple either.
     1We already have a client library for apps that want to use the Java I2P APIs, and it can be used with either a remote router via I2CP, or I2P Android via a !DomainSocket (which the client library handles). But there is a third option: bundle a router and use that. Bote currently bundles router.jar itself; it's not hard to do, but it isn't dead simple either.
    22
    33Bundling a router is IMHO a good idea to decrease the barrier to using an app. But running multiple routers on a single device is a bad idea. So I propose that the router code in I2P Android be extracted out into a router library, which additionally would contain code to detect multiple instances of itself (and distinguish between I2P Android instances and router lib instances). Then we provide it as the recommended way to bundle an I2P router inside an app. If a user installs two apps that both bundle routers, but doesn't have I2P Android installed, the router lib will automatically prompt them to install I2P Android, and will prevent itself from starting if an I2P router is already running.