/**@class android.nfc.NdefMessage
 implements android.os.Parcelable

@extends java.lang.Object

 Represents an immutable NDEF Message.
 <p>
 NDEF (NFC Data Exchange Format) is a light-weight binary format,
 used to encapsulate typed data. It is specified by the NFC Forum,
 for transmission and storage with NFC, however it is transport agnostic.
 <p>
 NDEF defines messages and records. An NDEF Record contains
 typed data, such as MIME-type media, a URI, or a custom
 application payload. An NDEF Message is a container for
 one or more NDEF Records.
 <p>
 When an Android device receives an NDEF Message
 (for example by reading an NFC tag) it processes it through
 a dispatch mechanism to determine an activity to launch.
 The type of the <em>first</em> record in the message has
 special importance for message dispatch, so design this record
 carefully.
 <p>
 Use {@link #NdefMessage(byte[])} to construct an NDEF Message from
 binary data, or {@link #NdefMessage(NdefRecord[])} to
 construct from one or more {@link android.nfc.NdefRecord}s.
 <p class="note">
 {@link android.nfc.NdefMessage} and {@link android.nfc.NdefRecord} implementations are
 always available, even on Android devices that do not have NFC hardware.
 <p class="note">
 {@link android.nfc.NdefRecord}s are intended to be immutable (and thread-safe),
 however they may contain mutable fields. So take care not to modify
 mutable fields passed into constructors, or modify mutable fields
 obtained by getter methods, unless such modification is explicitly
 marked as safe.

 @see NfcAdapter#ACTION_NDEF_DISCOVERED
 @see NdefRecord
*/
var NdefMessage = {

/***/
CREATOR : "null",
/**Get the NDEF Records inside this NDEF Message.<p>
 An {@link android.nfc.NdefMessage} always has one or more NDEF Records: so the
 following code to retrieve the first record is always safe
 (no need to check for null or array length >= 1):
 <pre>
 NdefRecord firstRecord = ndefMessage.getRecords()[0];
 </pre>
@return {Object {android.nfc.NdefRecord}} array of one or more NDEF records.
*/
getRecords : function(  ) {},

/**Return the length of this NDEF Message if it is written to a byte array
 with {@link #toByteArray}.<p>
 An NDEF Message can be formatted to bytes in different ways
 depending on chunking, SR, and ID flags, so the length returned
 by this method may not be equal to the length of the original
 byte array used to construct this NDEF Message. However it will
 always be equal to the length of the byte array produced by
 {@link #toByteArray}.
@return {Number} length of this NDEF Message when written to bytes with {@link #toByteArray}
@see #toByteArray
*/
getByteArrayLength : function(  ) {},

/**Return this NDEF Message as raw bytes.<p>
 The NDEF Message is formatted as per the NDEF 1.0 specification,
 and the byte array is suitable for network transmission or storage
 in an NFC Forum NDEF compatible tag.<p>
 This method will not chunk any records, and will always use the
 short record (SR) format and omit the identifier field when possible.
@return {Number} NDEF Message in binary format
@see #getByteArrayLength()
*/
toByteArray : function(  ) {},

/**
*/
describeContents : function(  ) {},

/**
*/
writeToParcel : function(  ) {},

/**
*/
hashCode : function(  ) {},

/**Returns true if the specified NDEF Message contains
 identical NDEF Records.
*/
equals : function(  ) {},

/**
*/
toString : function(  ) {},


};