Android-DDP 0,0 editorconfig

Meteor's Distributed Data Protocol (DDP) for clients on Android

Android-DDP

This library implements the Distributed Data Protocol (DDP) from Meteor for clients on Android.

Connect your native Android apps, written in Java, to apps built with the Meteor framework and build real-time features.

Motivation

  • Have you built a web application with Meteor?
    • Using this library, you can build native Android apps that can talk to your Meteor server and web application.
  • Are you primarily an Android developer (who has never heard of Meteor)?
    • With “Android-DDP”, you can use a Meteor server as your backend for real-time applications on Android.
  • Doesn’t Meteor provide built-in features for Android app development already?
    • With Meteor’s built-in features, your Android app will be written in HTML, CSS and JavaScript, wrapped in a WebView. It will not be a native app.
    • By using this library, however, you can write native Android apps in Java while still using Meteor as your real-time backend.

Requirements

  • Android 2.3+

Installation

  • Add this library to your project

    • Declare the Gradle repository in your root build.gradle
     allprojects {
         repositories {
             maven { url "https://jitpack.io" }
         }
     }
    
    • Declare the Gradle dependency in your app module’s build.gradle
     dependencies {
         compile 'com.github.delight-im:Android-DDP:v3.1.2'
     }
    
  • Add the Internet permission to your app’s AndroidManifest.xml:

    <uses-permission android:name="android.permission.INTERNET" />
    

Usage

  • Creating a new instance of the DDP client
   public class MyActivity extends Activity implements MeteorCallback {

       private Meteor mMeteor;

       @Override
       protected void onCreate(Bundle savedInstanceState) {
           super.onCreate(savedInstanceState);

           // ...

           // create a new instance
           mMeteor = new Meteor(this, "ws://example.meteor.com/websocket");

           // register the callback that will handle events and receive messages
           mMeteor.addCallback(this);

           // establish the connection
           mMeteor.connect();
       }

       public void onConnect(boolean signedInAutomatically) { }

       public void onDisconnect() { }

       public void onDataAdded(String collectionName, String documentID, String newValuesJson) {
           // parse the JSON and manage the data yourself (not recommended)
           // or
           // enable a database (see section "Using databases to manage data") (recommended)
       }

       public void onDataChanged(String collectionName, String documentID, String updatedValuesJson, String removedValuesJson) {
           // parse the JSON and manage the data yourself (not recommended)
           // or
           // enable a database (see section "Using databases to manage data") (recommended)
       }

       public void onDataRemoved(String collectionName, String documentID) {
           // parse the JSON and manage the data yourself (not recommended)
           // or
           // enable a database (see section "Using databases to manage data") (recommended)
       }

       public void onException(Exception e) { }

       @Override
       public void onDestroy() {
           mMeteor.disconnect();
           mMeteor.removeCallback(this);
           // or
           // mMeteor.removeCallbacks();

           // ...

           super.onDestroy();
       }

   }
  • Singleton access

    • Creating an instance at the beginning
     MeteorSingleton.createInstance(this, "ws://example.meteor.com/websocket")
     // instead of
     // new Meteor(this, "ws://example.meteor.com/websocket")
    
    • Accessing the instance afterwards (across Activity instances)
     MeteorSingleton.getInstance()
     // instead of
     // mMeteor
    
    • All other API methods can be called on MeteorSingleton.getInstance() just as you would do on any other Meteor instance, as documented here with mMeteor
  • Registering a callback

   // MeteorCallback callback;
   mMeteor.addCallback(callback);
  • Unregistering a callback
   mMeteor.removeCallbacks();
   // or
   // // MeteorCallback callback;
   // mMeteor.removeCallback(callback);
  • Inserting data into a collection
   Map<String, Object> values = new HashMap<String, Object>();
   values.put("_id", "my-id");
   values.put("some-key", "some-value");

   mMeteor.insert("my-collection", values);
   // or
   // mMeteor.insert("my-collection", values, new ResultListener() { });
  • Updating data in a collection
   Map<String, Object> query = new HashMap<String, Object>();
   query.put("_id", "my-id");

   Map<String, Object> values = new HashMap<String, Object>();
   values.put("some-key", "some-value");

   mMeteor.update("my-collection", query, values);
   // or
   // mMeteor.update("my-collection", query, values, options);
   // or
   // mMeteor.update("my-collection", query, values, options, new ResultListener() { });
  • Deleting data from a collection
   mMeteor.remove("my-collection", "my-id");
   // or
   // mMeteor.remove("my-collection", "my-id", new ResultListener() { });
  • Subscribing to data from the server
   String subscriptionId = mMeteor.subscribe("my-subscription");
   // or
   // String subscriptionId = mMeteor.subscribe("my-subscription", new Object[] { arg1, arg2 });
   // or
   // String subscriptionId = mMeteor.subscribe("my-subscription", new Object[] { arg1, arg2 }, new SubscribeListener() { });
  • Unsubscribing from a previously established subscription
   mMeteor.unsubscribe(subscriptionId);
   // or
   // mMeteor.unsubscribe(subscriptionId, new UnsubscribeListener() { });
  • Calling a custom method defined on the server
   mMeteor.call("myMethod");
   // or
   // mMeteor.call("myMethod", new Object[] { arg1, arg2 });
   // or
   // mMeteor.call("myMethod", new ResultListener() { });
   // or
   // mMeteor.call("myMethod", new Object[] { arg1, arg2 }, new ResultListener() { });
  • Disconnect from the server
   mMeteor.disconnect();
  • Creating a new account (requires accounts-password package)
   mMeteor.registerAndLogin("john", "[email protected]", "password", new ResultListener() { });
   // or
   // mMeteor.registerAndLogin("john", "[email protected]", "password", profile, new ResultListener() { });
  • Signing in with an existing username (requires accounts-password package)
   mMeteor.loginWithUsername("john", "password", new ResultListener() { });
  • Signing in with an existing email address (requires accounts-password package)
   mMeteor.loginWithEmail("[email protected]", "password", new ResultListener() { });
  • Check if the client is currently logged in (requires accounts-password package)
   mMeteor.isLoggedIn();
  • Get the client’s user ID (if currently logged in) (requires accounts-password package)
   mMeteor.getUserId();
  • Logging out (requires accounts-password package)
   mMeteor.logout();
   // or
   // mMeteor.logout(new ResultListener() { });
  • Checking whether the client is connected
   mMeteor.isConnected();
  • Manually attempt to re-connect (if necessary)
   mMeteor.reconnect();

Using databases to manage data

Enabling a database

Pass an instance of Database to the constructor. Right now, the only subclass provided as a built-in database is InMemoryDatabase. So the code for the constructor becomes:

mMeteor = new Meteor(this, "ws://example.meteor.com/websocket", new InMemoryDatabase());

After that change, all data received from the server will automatically be parsed, updated and managed for you in the built-in database. That means no manual JSON parsing!

So whenever you receive data notifications via onDataAdded, onDataChanged or onDataRemoved, that data has already been merged into the database and can be retrieved from there. In these callbacks, you can thus ignore the parameters containing JSON data and instead get the data from your database.

Accessing the database

Database database = mMeteor.getDatabase();

This method call and most of the following method calls can be chained for simplicity.

Getting a collection from the database by name

// String collectionName = "myCollection";
Collection collection = mMeteor.getDatabase().getCollection(collectionName);

Retrieving the names of all collections from the database

String[] collectionNames = mMeteor.getDatabase().getCollectionNames();

Fetching the number of collections from the database

int numCollections = mMeteor.getDatabase().count();

Getting a document from a collection by ID

// String documentId = "wjQvNQ6sGjzLMDyiJ";
Document document = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId);

Retrieving the IDs of all documents from a collection

String[] documentIds = mMeteor.getDatabase().getCollection(collectionName).getDocumentIds();

Fetching the number of documents from a collection

int numDocuments = mMeteor.getDatabase().getCollection(collectionName).count();

Querying a collection for documents

Any of the following method calls can be chained and combined in any way to select documents via complex queries.

// String fieldName = "age";
// int fieldValue = 62;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereEqual(fieldName, fieldValue);
// String fieldName = "active";
// int fieldValue = false;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereNotEqual(fieldName, fieldValue);
// String fieldName = "accountBalance";
// float fieldValue = 100000.00f;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereLessThan(fieldName, fieldValue);
// String fieldName = "numChildren";
// long fieldValue = 3L;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereLessThanOrEqual(fieldName, fieldValue);
// String fieldName = "revenue";
// double fieldValue = 0.00;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereGreaterThan(fieldName, fieldValue);
// String fieldName = "age";
// int fieldValue = 21;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereGreaterThanOrEqual(fieldName, fieldValue);
// String fieldName = "address";
Query query = mMeteor.getDatabase().getCollection(collectionName).whereNull(fieldName);
// String fieldName = "modifiedAt";
Query query = mMeteor.getDatabase().getCollection(collectionName).whereNotNull(fieldName);

Any query can be executed by a find or findOne call. The step of first creating the Query instance can be skipped if you chain the calls to execute the query immediately.

Document[] documents = mMeteor.getDatabase().getCollection(collectionName).find();
// int limit = 30;
Document[] documents = mMeteor.getDatabase().getCollection(collectionName).find(limit);
// int limit = 30;
// int offset = 5;
Document[] documents = mMeteor.getDatabase().getCollection(collectionName).find(limit, offset);
Document document = mMeteor.getDatabase().getCollection(collectionName).findOne();

Chained together, these calls may look as follows, for example:

Document document = mMeteor.getDatabase().getCollection("users").whereNotNull("lastLoginAt").whereGreaterThan("level", 3).findOne();

Getting a field from a document by name

// String fieldName = "age";
Object field = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId).getField(fieldName);

Retrieving the names of all fields from a document

String[] fieldNames = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId).getFieldNames();

Fetching the number of fields from a document

int numFields = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId).count();

Contributing

All contributions are welcome! If you wish to contribute, please create an issue first so that your feature, problem or question can be discussed.

Dependencies

Further reading

Disclaimer

This project is neither affiliated with nor endorsed by Meteor.

License

Copyright (c) delight.im <[email protected]>

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Related Repositories

Android-DDP

Android-DDP

Meteor's Distributed Data Protocol (DDP) for clients on Android ...

android-ddp-client

android-ddp-client

Android DDP Client library to implement native client for Meteor.js server ...

MeteorPartiesDDPClient

MeteorPartiesDDPClient

Android native client to Meteor.js' Parties sample web site that shows how to use the android-ddp-client library ...

Android-DDP-WSS

Android-DDP-WSS

A fork of delight-im/Android-DDP to provide WSS support. ...


Top Contributors

ocram joshuaswett victorjmarin

Releases

-   v3.1.2 zip tar
-   v3.1.1 zip tar
-   v3.1.0 zip tar
-   v3.0.0 zip tar
-   v2.1.0 zip tar
-   v2.0.0 zip tar
-   v1.0.1 zip tar
-   v1.0.0 zip tar