Client programs often react to changes or updates that occur in a server. For example, a client graph or spreadsheet program might need to be updated with each stock price update on a stock market server. The client has two options in this scenario:
The example in this document illustrates how a client program can pass a callback object to a server, and the server can then callback to notify changes to the client. At this time, we have provided the code for an extension of a simple application. Notes about simplifying the application are contained within the code.
This document provides the code for:
Instructions for compiling and running the example are also provided.
For the example application, the file callback.idl looks like this:
interface Listener { void message(in string msg); }; interface MessageServer { void register(in Listener lt); };
For the example application, the Server.java file looks like as follows.
import org.omg.CORBA.ORB; import org.omg.PortableServer.POA; import org.omg.PortableServer.POAHelper; import org.omg.CosNaming.NameComponent; import org.omg.CosNaming.NamingContext; import org.omg.CosNaming.NamingContextHelper; public class Server { public static void main(String[] args) { try { //create and initialize the ORB Properties props = System.getProperties(); props.put("org.omg.CORBA.ORBInitialPort", "1050"); //Replace MyHost with the name of the host on which you are running the server props.put("org.omg.CORBA.ORBInitialHost", "<MyHost>"); ORB orb = ORB.init(args, props); System.out.println("Initialized ORB"); //Instantiate Servant and create reference POA rootPOA = POAHelper.narrow( orb.resolve_initial_references("RootPOA")); MessageServerImpl msImpl = new MessageServerImpl(); rootPOA.activate_object(msImpl); MessageServer msRef = MessageServerHelper.narrow( rootPOA.servant_to_reference(msImpl)); //Bind reference with NameService NamingContext namingContext = NamingContextHelper.narrow( orb.resolve_initial_references("NameService")); System.out.println("Resolved NameService"); NameComponent[] nc = { new NameComponent("MessageServer", "") }; namingContext.rebind(nc, msRef); //Activate rootpoa rootPOA.the_POAManager().activate(); //Start readthread and wait for incoming requests System.out.println("Server ready and running ...."); //REMOVE THE NEXT LINE FOR THE SIMPLER EXAMPLE msImpl.startReadThread(); orb.run(); } catch (Exception e) { e.printStackTrace(); } } }
The file registers new clients, accepts messages, then relays the messages to the registered clients. For the example application, the file MessageServerImpl.java looks like the following example.
import java.io.BufferedReader; import java.io.InputStreamReader; import java.util.Vector; import java.util.Iterator; public class MessageServerImpl extends MessageServerPOA { private Vector clients = new Vector(); private ReadThread rt = null; public MessageServerImpl() { rt = new ReadThread(this); } public void register(Listener lt) { clients.add(lt); } public void startReadThread() { rt.start(); } public void message(String msg) { Iterator it = clients.iterator(); while (it.hasNext()) { Listener lt = (Listener) it.next(); lt.message(msg); //FOR THE SIMPLER EXAMPLE, ADD A SIMPLE //MESSAGE TO BE CALLED BACK, FOR EXAMPLE, //SLEEP FOR 30 SECONDS, THEN SEND THE TIME } } } //EXCLUDE THIS CLASS FOR THE SIMPLER EXAMPLE class ReadThread extends Thread { MessageServerImpl msImpl = null; public ReadThread(MessageServerImpl msImpl) { this.msImpl = msImpl; } public void run() { BufferedReader br = new BufferedReader( new InputStreamReader(System.in)); try { for (;;) { System.out.print("message > "); String msg = br.readLine(); msImpl.message(msg); } } catch (Exception e) { e.printStackTrace(); } } }
For the example application, the file Client.java file looks like the following example.
import java.util.Properties; import org.omg.CORBA.ORB; import org.omg.PortableServer.POA; import org.omg.PortableServer.POAHelper; import org.omg.CosNaming.NameComponent; import org.omg.CosNaming.NamingContext; import org.omg.CosNaming.NamingContextHelper; public class Client { public static void main(String[] args) { try { //initialize orb Properties props = System.getProperties(); props.put("org.omg.CORBA.ORBInitialPort", "1050"); //Replace MyHost with the name of the host on which you are running the server props.put("org.omg.CORBA.ORBInitialHost", "<MyHost>"); ORB orb = ORB.init(args, props); System.out.println("Initialized ORB"); //Instantiate Servant and create reference POA rootPOA = POAHelper.narrow( orb.resolve_initial_references("RootPOA")); ListenerImpl listener = new ListenerImpl(); rootPOA.activate_object(listener); Listener ref = ListenerHelper.narrow( rootPOA.servant_to_reference(listener)); //Resolve MessageServer MessageServer msgServer = MessageServerHelper.narrow( orb.string_to_object("corbaname:iiop:1.2@localhost:1050#MessageServer")); //Register listener reference (callback object) with MessageServer msgServer.register(ref); System.out.println("Listener registered with MessageServer"); //Activate rootpoa rootPOA.the_POAManager().activate(); //Wait for messages System.out.println("Wait for incoming messages"); orb.run(); } catch (Exception e) { e.printStackTrace(); } } }
When the Listener identifies that a message has been received from the server, it displays the message on the client. For the example application, the ListenerImpl.java file looks like the following example.
public class ListenerImpl extends ListenerPOA { public void message(String msg) { System.out.println("Message from server : " + msg); } }
rm -rf ./classes ./orb.db
mkdir -p ./classes <path_to_java>/bin/idlj -fall -td ./classes callback.idl
<path_to_java>/bin/javac -classpath ./classes -d ./classes *.java
<path_to_java>/bin/orbd -ORBInitialPort 1050 -ORBInitialHost <host_name> &
<path_to_java>/bin/java -classpath ./classes Server -ORBInitialPort 1050
After you have started the server, you will see output such as the following in the terminal window:
Initialized ORB Resolved NameService Server ready and running .... message >
At this prompt, you will send messages to the client, but first you need to start the client application. From the CLIENT terminal, follow these steps to run the client. Make sure that you used the host name on which the server is running in the properties section of the client code.
<path_to_java>/bin/java -classpath ./classes Client -ORBInitialPort 1050
The output from the client will display in a format similar to this:
Initialized ORB Listener registered with MessageServer Wait for incoming messages
To display the functionality of using a callback, you would enter a data on the server terminal, at the prompt, and it will display on all client terminals. This could be anything where clients are interested in some notifications.
One example is a football game score where clients are notified whenever the score changes.
message > Niners TD. Niners 7 - Giants 0 message > Giants TD. Niners 7 - Giants 7 message > Niners TD. Niners 14 - Giants 7
When messages such as those shown above are sent, the client display looks similar to the following:
Wait for incoming messages Message from server : Niners TD. Niners 7 - Giants 0 Message from server : Giants TD. Niners 7 - Giants 7 Message from server : Niners TD. Niners 14 - Giants 7


List pin on current page or List all pins on all pages
- a placeholder pin from this page
- a placeholder pin from this page
- a placeholder pin from another page
- another placeholder pin from another page


RONIN Reviewed by Pierce Dalton 3 stars (out of 4)
Ronin is a very complicated film.
It is also a very slick, imaginative, thrilling film from director John Frankenheimer, whose 1996's film, Island of Dr. Moreau, left little to be desired.
The plot involves a bunch of international operatives (some ex-KGB) joining together to steal a briefcase away from a very powerful and wealthy man.
What's in the briefcase we don't know. Neither does Sam (Robert De Niro), the so-called leader of the operative group.
If you're thinking that bit resembles Pulp Fiction, you're not alone.
Tailing the briefcase all over Europe, Sam and his elite group (including Jean Reno) set up all kinds of booby traps and whatnots to trap the man and briefcase. The film has a sort of James Bond feel to it, yet, generates more energy from its action sequences than any 007 film I have seen, including 1997's Tomorrow Never Dies.
De Niro and Reno work great together. They have that rare flare for acting that never goes stale, even in the midst of a film like Ronin, which, if you get right down to it, is very intelligent, atmospheric, and dopey.
One thing that really heightens the film to intensity are its spectacular car chase scenes. They are among the best I have seen.
A long drawn-out one, featured in the now-famed tunnel where Princess Diana died in Paris, is a dizzying, frenzied, pure rush or energy.
Director Frankenheimer has abandoned Moreau's Island and created a very sassy thriller, and some breathtaking views, in Paris and Rome.
Do Sam and the gang capture the briefcase?
I won't tell.
See for yourself.
You'll never look at a car the came again.
1999<EMAIL_ADDRESS>The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


|
OpenM++ runtime library (libopenm)
|
model_dic table row and default model language code. More...
Public Attributes | |
| string | defaultLangCode |
| default model language code | |
| Public Attributes inherited from openm::ModelDicRow | |
| int | modelId |
| model_id INT NOT NULL | |
| string | name |
| model_name VARCHAR(255) NOT NULL | |
| string | digest |
| model_digest VARCHAR(32) NOT NULL | |
| int | type |
| model_type INT NOT NULL | |
| string | version |
| model_ver VARCHAR(32) NOT NULL | |
| string | createDateTime |
| create_dt VARCHAR(32) NOT NULL | |
| int | defaultLangId |
| default_lang_id INT NOT NULL | |
Additional Inherited Members | |
| Public Member Functions inherited from openm::ModelDicRow | |
| ModelDicRow (int i_modelId) | |
| create row with supplied primary key field values. | |
| ModelDicRow (void) | |
| create row with default empty field values. | |
| Static Public Member Functions inherited from openm::ModelDicRow | |
| static bool | isKeyLess (const ModelDicRow &i_left, const ModelDicRow &i_right) |
| less comparator by primary key: model id. | |
| static bool | isKeyEqual (const ModelDicRow &i_left, const ModelDicRow &i_right) |
| equal comparator by primary key: model id. | |
| Static Public Member Functions inherited from openm::IMetaRow< ModelDicRow > | |
| static bool | keyLess (const IRowBaseUptr &i_left, const IRowBaseUptr &i_right) |
| less comparator by row primary key. | |
| static bool | keyEqual (const IRowBaseUptr &i_left, const IRowBaseUptr &i_right) |
| equal comparator by row primary key. | |
model_dic table row and default model language code.


Given a valid region name, return a boto.rds2.layer1.RDSConnection. Any additional parameters after the region_name are passed on to the connect method of the region object.
| Type: | str |
|---|---|
| Parameters: | region_name – The name of the region to connect to. |
| Return type: | boto.rds2.layer1.RDSConnection or None |
| Returns: | A connection to the given region, or None if an invalid region name is given |
Get all available regions for the RDS service.
| Return type: | list |
|---|---|
| Returns: | A list of boto.regioninfo.RegionInfo |
Amazon Relational Database Service Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the cloud. It provides cost-efficient, resizable capacity for an industry-standard relational database and manages common database administration tasks, freeing up developers to focus on what makes their applications and businesses unique.
Amazon RDS gives you access to the capabilities of a familiar MySQL or Oracle database server. This means the code, applications, and tools you already use today with your existing MySQL or Oracle databases work with Amazon RDS without modification. Amazon RDS automatically backs up your database and maintains the database software that powers your DB instance. Amazon RDS is flexible: you can scale your database instance’s compute resources and storage capacity to meet your application’s demand. As with all Amazon Web Services, there are no up-front investments, and you pay only for the resources you use.
This is the Amazon RDS API Reference . It contains a comprehensive description of all Amazon RDS Query APIs and data types. Note that this API is asynchronous and some actions may require polling to determine when an action has been applied. See the parameter description to determine if a change is applied immediately or on the next instance reboot or during the maintenance window. For more information on Amazon RDS concepts and usage scenarios, go to the `Amazon RDS User Guide`_.
alias of JSONResponseError
Adds a source identifier to an existing RDS event notification subscription.
| Parameters: |
|---|
Constraints:
must be supplied.
must be supplied.
must be supplied.
supplied.
Adds metadata tags to an Amazon RDS resource. These tags can also be used with cost allocation reporting to track cost associated with Amazon RDS resources, or used in Condition statement in IAM policy for Amazon RDS.
For an overview on tagging Amazon RDS resources, see `Tagging Amazon RDS Resources`_.
| Parameters: |
|---|
Enables ingress to a DBSecurityGroup using one of two forms of authorization. First, EC2 or VPC security groups can be added to the DBSecurityGroup if the application using the database is running on EC2 or VPC instances. Second, IP ranges are available if the application accessing your database is running on the Internet. Required parameters for this API are one of CIDR range, EC2SecurityGroupId for VPC, or (EC2SecurityGroupOwnerId and either EC2SecurityGroupName or EC2SecurityGroupId for non-VPC). You cannot authorize ingress from an EC2 security group in one Region to an Amazon RDS DB instance in another. You cannot authorize ingress from a VPC security group in one VPC to an Amazon RDS DB instance in another. For an overview of CIDR ranges, go to the `Wikipedia Tutorial`_.
| Parameters: |
|
|---|
Copies the specified DBSnapshot. The source DBSnapshot must be in the “available” state.
| Parameters: | source_db_snapshot_identifier (string) – The identifier for the source DB snapshot. |
|---|
Constraints:
state.
Example: rds:mydb-2012-04-02-00-01
| Parameters: | target_db_snapshot_identifier (string) – The identifier for the copied snapshot. |
|---|
Constraints:
Example: my-db-snapshot
| Parameters: | tags (list) – A list of tags. |
|---|
Creates a new DB instance.
| Parameters: | db_name (string) – The meaning of this parameter differs according to the database engine you use. |
|---|
MySQL
Constraints:
Type: String
Oracle
The Oracle System ID (SID) of the created DB instance.
Default: ORCL
Constraints:
SQL Server
Not applicable. Must be null.
| Parameters: | db_instance_identifier (string) – The DB instance identifier. This parameter is stored as a lowercase string. |
|---|
Constraints:
for SQL Server).
First character must be a letter.
Cannot end with a hyphen or contain two consecutive hyphens.
Example: mydbinstance
| Parameters: | allocated_storage (integer) – The amount of storage (in gigabytes) to be initially allocated for the database instance. |
|---|
MySQL
Constraints: Must be an integer from 5 to 1024.
Type: Integer
Oracle
Constraints: Must be an integer from 10 to 1024.
SQL Server
| Parameters: | db_instance_class (string) – The compute and memory capacity of the DB instance. |
|---|
| Parameters: | engine (string) – The name of the database engine to be used for this instance. |
|---|
| Parameters: | master_username (string) – |
|---|
The name of master user for the client DB instance.
MySQL
Constraints:
Type: String
Oracle
Constraints:
SQL Server
Constraints:
| Parameters: | master_user_password (string) – The password for the master database user. Can be any printable ASCII character except “/”, ‘”’, or “@”. |
|---|
Type: String
MySQL
Constraints: Must contain from 8 to 41 characters.
Oracle
Constraints: Must contain from 8 to 30 characters.
SQL Server
Constraints: Must contain from 8 to 128 characters.
| Parameters: | db_security_groups (list) – A list of DB security groups to associate with this DB instance. |
|---|
Default: The default DB security group for the database engine.
| Parameters: | vpc_security_group_ids (list) – A list of EC2 VPC security groups to associate with this DB instance. |
|---|
| Parameters: | availability_zone (string) – The EC2 Availability Zone that the database instance will be created in. |
|---|
Example: us-east-1d
| Parameters: | db_subnet_group_name (string) – A DB subnet group to associate with this DB instance. |
|---|
If there is no DB subnet group, then it is a non-VPC DB instance.
| Parameters: | preferred_maintenance_window (string) – The weekly time range (in UTC) during which system maintenance can occur. |
|---|
Format: ddd:hh24:mi-ddd:hh24:mi
Valid Days: Mon, Tue, Wed, Thu, Fri, Sat, Sun
Constraints: Minimum 30-minute window.
| Parameters: | db_parameter_group_name (string) – |
|---|
Constraints:
| Parameters: | backup_retention_period (integer) – |
|---|
Default: 1
Constraints:
Must be a value from 0 to 8
replicas
| Parameters: | preferred_backup_window (string) – The daily time range during which automated backups are created if automated backups are enabled, using the BackupRetentionPeriod parameter. |
|---|
| Parameters: | port (integer) – The port number on which the database accepts connections. |
|---|
MySQL
Default: 3306
Valid Values: 1150-65535
Type: Integer
Oracle
Default: 1521
Valid Values: 1150-65535
SQL Server
Default: 1433
Valid Values: 1150-65535 except for 1434 and 3389.
| Parameters: |
|
|---|
MySQL
Example: 5.1.42
Type: String
Oracle
Example: <IP_ADDRESS>.v2
Type: String
SQL Server
Example: 10.50.2789.0.v1
| Parameters: | auto_minor_version_upgrade (boolean) – Indicates that minor engine upgrades will be applied automatically to the DB instance during the maintenance window. |
|---|
Default: True
| Parameters: | license_model (string) – License model information for this DB instance. |
|---|
| Parameters: | iops (integer) – The amount of Provisioned IOPS (input/output operations per second) to be initially allocated for the DB instance. |
|---|
Constraints: Must be an integer greater than 1000.
| Parameters: | option_group_name (string) – Indicates that the DB instance should be associated with the specified option group. |
|---|
| Parameters: |
|
|---|
| Parameters: | tags (list) – A list of tags. |
|---|
Creates a DB instance that acts as a read replica of a source DB instance.
All read replica DB instances are created as Single-AZ deployments with backups disabled. All other DB instance attributes (including DB security groups and DB parameter groups) are inherited from the source DB instance, except as specified below.
The source DB instance must have backup retention enabled.
| Parameters: |
|
|---|
| Parameters: | db_instance_class (string) – The compute and memory capacity of the read replica. |
|---|
Default: Inherits from the source DB instance.
| Parameters: | availability_zone (string) – The Amazon EC2 Availability Zone that the read replica will be created in. |
|---|
Example: us-east-1d
| Parameters: | port (integer) – The port number that the DB instance uses for connections. |
|---|
Default: Inherits from the source DB instance
Valid Values: 1150-65535
| Parameters: | auto_minor_version_upgrade (boolean) – Indicates that minor engine upgrades will be applied automatically to the read replica during the maintenance window. |
|---|
Default: Inherits from the source DB instance
| Parameters: |
|
|---|
| Parameters: | tags (list) – A list of tags. |
|---|
Creates a new DB parameter group.
A DB parameter group is initially created with the default parameters for the database engine used by the DB instance. To provide custom values for any of the parameters, you must modify the group after creating it using ModifyDBParameterGroup . Once you’ve created a DB parameter group, you need to associate it with your DB instance using ModifyDBInstance . When you associate a new DB parameter group with a running DB instance, you need to reboot the DB Instance for the new DB parameter group and associated settings to take effect.
| Parameters: | db_parameter_group_name (string) – |
|---|
The name of the DB parameter group.
Constraints:
This value is stored as a lower-case string.
| Parameters: |
|
|---|
Creates a new DB security group. DB security groups control access to a DB instance.
| Parameters: | db_security_group_name (string) – The name for the DB security group. This value is stored as a lowercase string. |
|---|
Constraints:
Example: mysecuritygroup
| Parameters: |
|---|
Creates a DBSnapshot. The source DBInstance must be in “available” state.
| Parameters: | db_snapshot_identifier (string) – The identifier for the DB snapshot. |
|---|
Constraints:
Example: my-snapshot-id
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: | tags (list) – A list of tags. |
|---|
Creates a new DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the region.
| Parameters: | db_subnet_group_name (string) – The name for the DB subnet group. This value is stored as a lowercase string. |
|---|
Example: mySubnetgroup
| Parameters: |
|---|
Creates an RDS event notification subscription. This action requires a topic ARN (Amazon Resource Name) created by either the RDS console, the SNS console, or the SNS API. To obtain an ARN with SNS, you must create a topic in Amazon SNS and subscribe to the topic. The ARN is displayed in the SNS console.
You can specify the type of source (SourceType) you want to be notified of, provide a list of RDS sources (SourceIds) that triggers the events, and provide a list of event categories (EventCategories) for events you want to be notified of. For example, you can specify SourceType = db-instance, SourceIds = mydbinstance1, mydbinstance2 and EventCategories = Availability, Backup.
If you specify both the SourceType and SourceIds, such as SourceType = db-instance and SourceIdentifier = myDBInstance1, you will be notified of all the db-instance events for the specified source. If you specify a SourceType but do not specify a SourceIdentifier, you will receive notice of the events for that source type for all your RDS sources. If you do not specify either the SourceType nor the SourceIdentifier, you will be notified of events generated from all RDS sources belonging to your customer account.
| Parameters: | subscription_name (string) – The name of the subscription. |
|---|
Constraints: The name must be less than 255 characters.
| Parameters: |
|
|---|
| Parameters: |
|---|
Constraints:
If SourceIds are supplied, SourceType must also be provided.
must be supplied.
must be supplied.
must be supplied.
supplied.
| Parameters: |
|
|---|
Creates a new option group. You can create up to 20 option groups.
| Parameters: | option_group_name (string) – Specifies the name of the option group to be created. |
|---|
Constraints:
Example: myoptiongroup
| Parameters: |
|
|---|
The DeleteDBInstance action deletes a previously provisioned DB instance. A successful response from the web service indicates the request was received correctly. When you delete a DB instance, all automated backups for that instance are deleted and cannot be recovered. Manual DB snapshots of the DB instance to be deleted are not deleted.
If a final DB snapshot is requested the status of the RDS instance will be “deleting” until the DB snapshot is created. The API action DescribeDBInstance is used to monitor the status of this operation. The action cannot be canceled or reverted once submitted.
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: | skip_final_snapshot (boolean) – Determines whether a final DB snapshot is created before the DB instance is deleted. If True is specified, no DBSnapshot is created. If false is specified, a DB snapshot is created before the DB instance is deleted. |
|---|
Default: False
| Parameters: | final_db_snapshot_identifier (string) – |
|---|
Constraints:
Deletes a specified DBParameterGroup. The DBParameterGroup cannot be associated with any RDS instances to be deleted. The specified DB parameter group cannot be associated with any DB instances.
| Parameters: | db_parameter_group_name (string) – |
|---|
The name of the DB parameter group.
Constraints:
Deletes a DB security group. The specified DB security group must not be associated with any DB instances.
| Parameters: | db_security_group_name (string) – |
|---|
The name of the DB security group to delete.
You cannot delete the default DB security group.
Constraints:
Deletes a DBSnapshot. The DBSnapshot must be in the available state to be deleted.
| Parameters: | db_snapshot_identifier (string) – The DBSnapshot identifier. |
|---|
Deletes a DB subnet group. The specified database subnet group must not be associated with any DB instances.
| Parameters: | db_subnet_group_name (string) – |
|---|
The name of the database subnet group to delete.
You cannot delete the default subnet group.
Constraints:
Deletes an RDS event notification subscription.
| Parameters: | subscription_name (string) – The name of the RDS event notification subscription you want to delete. |
|---|
Deletes an existing option group.
| Parameters: | option_group_name (string) – |
|---|
The name of the option group to be deleted.
You cannot delete default option groups.
Returns a list of the available DB engines.
| Parameters: |
|---|
Example: 5.1.49
| Parameters: | db_parameter_group_family (string) – |
|---|
The name of a specific DB parameter group family to return details for.
Constraints:
| Parameters: | max_records (integer) – The maximum number of records to include in the response. If more than the MaxRecords value is available, a pagination token called a marker is included in the response so that the following results can be retrieved. |
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: |
|
|---|
Returns information about provisioned RDS instances. This API supports pagination.
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeDBInstances request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords . |
|---|
Returns a list of DB log files for the DB instance.
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: |
|
|---|
Returns a list of DBParameterGroup descriptions. If a DBParameterGroupName is specified, the list will contain only the description of the specified DB parameter group.
| Parameters: | db_parameter_group_name (string) – |
|---|
The name of a specific DB parameter group to return details for.
Constraints:
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeDBParameterGroups request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Returns the detailed parameter list for a particular DB parameter group.
| Parameters: | db_parameter_group_name (string) – |
|---|
The name of a specific DB parameter group to return details for.
Constraints:
| Parameters: | source (string) – The parameter types to return. |
|---|
Default: All parameter types returned
Valid Values: user | system | engine-default
| Parameters: | max_records (integer) – The maximum number of records to include in the response. If more records exist than the specified MaxRecords value, a pagination token called a marker is included in the response so that the remaining results may be retrieved. |
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeDBParameters request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Returns a list of DBSecurityGroup descriptions. If a DBSecurityGroupName is specified, the list will contain only the descriptions of the specified DB security group.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeDBSecurityGroups request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Returns information about DB snapshots. This API supports pagination.
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: | db_snapshot_identifier (string) – |
|---|
Constraints:
Must be 1 to 255 alphanumeric characters
First character must be a letter
Cannot end with a hyphen or contain two consecutive hyphens
SnapshotType parameter must also be specified.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeDBSnapshots request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Returns a list of DBSubnetGroup descriptions. If a DBSubnetGroupName is specified, the list will contain only the descriptions of the specified DBSubnetGroup.
For an overview of CIDR ranges, go to the `Wikipedia Tutorial`_.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeDBSubnetGroups request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Returns the default engine and system parameter information for the specified database engine.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeEngineDefaultParameters request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Displays a list of categories for all event source types, or, if specified, for a specified source type. You can see a list of the event categories and source types in the ` Events`_ topic in the Amazon RDS User Guide.
| Parameters: | source_type (string) – The type of source that will be generating the events. |
|---|
Lists all the subscription descriptions for a customer account. The description for a subscription includes SubscriptionName, SNSTopicARN, CustomerID, SourceType, SourceID, CreationTime, and Status.
If you specify a SubscriptionName, lists the description for that subscription.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeOrderableDBInstanceOptions request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords . |
|---|
Returns events related to DB instances, DB security groups, DB snapshots, and DB parameter groups for the past 14 days. Events specific to a particular DB instance, DB security group, database snapshot, or DB parameter group can be obtained by providing the name as a parameter. By default, the past hour of events are returned.
| Parameters: | source_identifier (string) – |
|---|
Constraints:
If SourceIdentifier is supplied, SourceType must also be provided.
must be supplied.
be supplied.
must be supplied.
supplied.
Cannot end with a hyphen or contain two consecutive hyphens.
| Parameters: |
|
|---|
Example: 2009-07-08T18:00Z
| Parameters: | end_time (timestamp) – The end of the time interval for which to retrieve events, specified in ISO 8601 format. For more information about ISO 8601, go to the `ISO8601 Wikipedia page.`_ |
|---|
Example: 2009-07-08T18:00Z
| Parameters: | duration (integer) – The number of minutes to retrieve events for. |
|---|
Default: 60
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeEvents request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Describes all available options.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Describes the available option groups.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: |
|
|---|
Returns a list of orderable DB instance options for the specified engine.
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous DescribeOrderableDBInstanceOptions request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords . |
|---|
Returns information about reserved DB instances for this account, or about a specified reserved DB instance.
| Parameters: |
|
|---|
Valid Values: 1 | 3 | 31536000 | 94608000
| Parameters: |
|
|---|
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Lists available reserved DB instance offerings.
| Parameters: | reserved_db_instances_offering_id (string) – The offering identifier filter value. Specify this parameter to show only the available offering that matches the specified reservation identifier. |
|---|
Example: 438012d3-4052-4cc7-b2e3-8d3372e0e706
| Parameters: |
|
|---|
Valid Values: 1 | 3 | 31536000 | 94608000
| Parameters: |
|
|---|
| Parameters: |
|
|---|
Default: 100
Constraints: minimum 20, maximum 100
| Parameters: | marker (string) – An optional pagination token provided by a previous request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords. |
|---|
Downloads the last line of the specified log file.
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: |
|
|---|
Lists all tags on an Amazon RDS resource.
For an overview on tagging an Amazon RDS resource, see `Tagging Amazon RDS Resources`_.
| Parameters: | resource_name (string) – The Amazon RDS resource with tags to be listed. This value is an Amazon Resource Name (ARN). For information about creating an ARN, see ` Constructing an RDS Amazon Resource Name (ARN)`_. |
|---|
Modify settings for a DB instance. You can change one or more database configuration parameters by specifying these parameters and the new values in the request.
| Parameters: | db_instance_identifier (string) – |
|---|
The DB instance identifier. This value is stored as a lowercase string.
Constraints:
| Parameters: | allocated_storage (integer) – The new storage capacity of the RDS instance. Changing this parameter does not result in an outage and the change is applied during the next maintenance window unless the ApplyImmediately parameter is set to True for this request. |
|---|
MySQL
Default: Uses existing setting
Valid Values: 5-1024
Type: Integer
Oracle
Default: Uses existing setting
Valid Values: 10-1024
SQL Server
Cannot be modified.
| Parameters: | db_instance_class (string) – The new compute and memory capacity of the DB instance. To determine the instance classes that are available for a particular DB engine, use the DescribeOrderableDBInstanceOptions action. |
|---|
Default: Uses existing setting
| Parameters: | db_security_groups (list) – |
|---|
Constraints:
| Parameters: | vpc_security_group_ids (list) – |
|---|
Constraints:
| Parameters: | apply_immediately (boolean) – Specifies whether or not the modifications in this request and any pending modifications are asynchronously applied as soon as possible, regardless of the PreferredMaintenanceWindow setting for the DB instance. |
|---|
Default: False
| Parameters: | master_user_password (string) – |
|---|
Default: Uses existing setting
| Parameters: | db_parameter_group_name (string) – The name of the DB parameter group to apply to this DB instance. Changing this parameter does not result in an outage and the change is applied during the next maintenance window unless the ApplyImmediately parameter is set to True for this request. |
|---|
Default: Uses existing setting
| Parameters: | backup_retention_period (integer) – |
|---|
Default: Uses existing setting
Constraints:
Must be a value from 0 to 8
replicas or if the DB instance is a read replica
| Parameters: | preferred_backup_window (string) – |
|---|
Constraints:
| Parameters: | preferred_maintenance_window (string) – The weekly time range (in UTC) during which system maintenance can occur, which may result in an outage. Changing this parameter does not result in an outage, except in the following situation, and the change is asynchronously applied as soon as possible. If there are pending actions that cause a reboot, and the maintenance window is changed to include the current time, then changing this parameter will cause a reboot of the DB instance. If moving this window to the current time, there must be at least 30 minutes between the current time and end of the window to ensure pending changes are applied. |
|---|
Default: Uses existing setting
Format: ddd:hh24:mi-ddd:hh24:mi
Valid Days: Mon | Tue | Wed | Thu | Fri | Sat | Sun
Constraints: Must be at least 30 minutes
| Parameters: | multi_az (boolean) – Specifies if the DB instance is a Multi-AZ deployment. Changing this parameter does not result in an outage and the change is applied during the next maintenance window unless the ApplyImmediately parameter is set to True for this request. |
|---|
Constraints: Cannot be specified if the DB instance is a read replica.
| Parameters: | engine_version (string) – The version number of the database engine to upgrade to. Changing this parameter results in an outage and the change is applied during the next maintenance window unless the ApplyImmediately parameter is set to True for this request. |
|---|
Example: 5.1.42
| Parameters: | allow_major_version_upgrade (boolean) – Indicates that major version upgrades are allowed. Changing this parameter does not result in an outage and the change is asynchronously applied as soon as possible. |
|---|
| Parameters: |
|
|---|
Default: Uses existing setting
Type: Integer
| Parameters: | option_group_name (string) – Indicates that the DB instance should be associated with the specified option group. Changing this parameter does not result in an outage except in the following case and the change is applied during the next maintenance window unless the ApplyImmediately parameter is set to True for this request. If the parameter change results in an option group that enables OEM, this change can cause a brief (sub-second) period during which new connections are rejected but existing connections are not interrupted. |
|---|
| Parameters: | new_db_instance_identifier (string) – |
|---|
Constraints:
Modifies the parameters of a DB parameter group. To modify more than one parameter, submit a list of the following: ParameterName, ParameterValue, and ApplyMethod. A maximum of 20 parameters can be modified in a single request.
The apply-immediate method can be used only for dynamic parameters; the pending-reboot method can be used with MySQL and Oracle DB instances for either dynamic or static parameters. For Microsoft SQL Server DB instances, the pending-reboot method can be used only for static parameters.
| Parameters: | db_parameter_group_name (string) – |
|---|
The name of the DB parameter group.
Constraints:
| Parameters: | parameters (list) – |
|---|
Valid Values (for the application method): immediate | pending-reboot
Modifies an existing DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the region.
| Parameters: | db_subnet_group_name (string) – The name for the DB subnet group. This value is stored as a lowercase string. |
|---|
Example: mySubnetgroup
| Parameters: |
|---|
Modifies an existing RDS event notification subscription. Note that you cannot modify the source identifiers using this call; to change source identifiers for a subscription, use the AddSourceIdentifierToSubscription and RemoveSourceIdentifierFromSubscription calls.
You can see a list of the event categories for a given SourceType in the `Events`_ topic in the Amazon RDS User Guide or by using the DescribeEventCategories action.
| Parameters: |
|
|---|
| Parameters: |
|
|---|
Modifies an existing option group.
| Parameters: | option_group_name (string) – The name of the option group to be modified. |
|---|
| Parameters: |
|
|---|
Promotes a read replica DB instance to a standalone DB instance.
| Parameters: | db_instance_identifier (string) – The DB instance identifier. This value is stored as a lowercase string. |
|---|
Constraints:
Example: mydbinstance
| Parameters: | backup_retention_period (integer) – |
|---|
Default: 1
Constraints:
| Parameters: | preferred_backup_window (string) – The daily time range during which automated backups are created if automated backups are enabled, using the BackupRetentionPeriod parameter. |
|---|
Purchases a reserved DB instance offering.
| Parameters: | reserved_db_instances_offering_id (string) – The ID of the Reserved DB instance offering to purchase. |
|---|
Example: 438012d3-4052-4cc7-b2e3-8d3372e0e706
| Parameters: | reserved_db_instance_id (string) – Customer-specified identifier to track this reservation. |
|---|
Example: myreservationID
| Parameters: | db_instance_count (integer) – The number of instances to reserve. |
|---|
Default: 1
| Parameters: | tags (list) – A list of tags. |
|---|
Rebooting a DB instance restarts the database engine service. A reboot also applies to the DB instance any modifications to the associated DB parameter group that were pending. Rebooting a DB instance results in a momentary outage of the instance, during which the DB instance status is set to rebooting. If the RDS instance is configured for MultiAZ, it is possible that the reboot will be conducted through a failover. An Amazon RDS event is created when the reboot is completed.
If your DB instance is deployed in multiple Availability Zones, you can force a failover from one AZ to the other during the reboot. You might force a failover to test the availability of your DB instance deployment or to restore operations to the original AZ after a failover occurs.
The time required to reboot is a function of the specific database engine’s crash recovery process. To improve the reboot time, we recommend that you reduce database activities as much as possible during the reboot process to reduce rollback activity for in-transit transactions.
| Parameters: | db_instance_identifier (string) – |
|---|
Constraints:
| Parameters: | force_failover (boolean) – When True, the reboot will be conducted through a MultiAZ failover. |
|---|
Removes a source identifier from an existing RDS event notification subscription.
| Parameters: |
|---|
Removes metadata tags from an Amazon RDS resource.
For an overview on tagging an Amazon RDS resource, see `Tagging Amazon RDS Resources`_.
| Parameters: |
|---|
Modifies the parameters of a DB parameter group to the engine/system default value. To reset specific parameters submit a list of the following: ParameterName and ApplyMethod. To reset the entire DB parameter group, specify the DBParameterGroup name and ResetAllParameters parameters. When resetting the entire group, dynamic parameters are updated immediately and static parameters are set to pending-reboot to take effect on the next DB instance restart or RebootDBInstance request.
| Parameters: | db_parameter_group_name (string) – |
|---|
The name of the DB parameter group.
Constraints:
| Parameters: | reset_all_parameters (boolean) – Specifies whether ( True) or not ( False) to reset all parameters in the DB parameter group to default values. |
|---|
Default: True
| Parameters: | parameters (list) – An array of parameter names, values, and the apply method for the parameter update. At least one parameter name, value, and apply method must be supplied; subsequent arguments are optional. A maximum of 20 parameters may be modified in a single request. |
|---|
MySQL
Valid Values (for Apply method): immediate | pending-reboot
Oracle
Valid Values (for Apply method): pending-reboot
Creates a new DB instance from a DB snapshot. The target database is created from the source database restore point with the same configuration as the original source database, except that the new RDS instance is created with the default security group.
| Parameters: | db_instance_identifier (string) – |
|---|
The identifier for the DB snapshot to restore from.
Constraints:
| Parameters: | db_snapshot_identifier (string) – Name of the DB instance to create from the DB snapshot. This parameter isn’t case sensitive. |
|---|
Constraints:
Example: my-snapshot-id
| Parameters: | db_instance_class (string) – The compute and memory capacity of the Amazon RDS DB instance. |
|---|
| Parameters: | port (integer) – The port number on which the database accepts connections. |
|---|
Default: The same port as the original DB instance
Constraints: Value must be 1150-65535
| Parameters: | availability_zone (string) – The EC2 Availability Zone that the database instance will be created in. |
|---|
Default: A random, system-chosen Availability Zone.
Example: us-east-1a
| Parameters: |
|
|---|
| Parameters: | publicly_accessible (boolean) – Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. |
|---|
| Parameters: |
|
|---|
Default: Same as source.
| Parameters: | db_name (string) – |
|---|
The database name for the restored DB instance.
This parameter doesn’t apply to the MySQL engine.
| Parameters: | engine (string) – The database engine to use for the new instance. |
|---|
Default: The same as source
Constraint: Must be compatible with the engine of the source
Example: oracle-ee
| Parameters: | iops (integer) – Specifies the amount of provisioned IOPS for the DB instance, expressed in I/O operations per second. If this parameter is not specified, the IOPS value will be taken from the backup. If this parameter is set to 0, the new instance will be converted to a non-PIOPS instance, which will take additional time, though your DB instance will be available for connections before the conversion starts. |
|---|
Constraints: Must be an integer greater than 1000.
| Parameters: | option_group_name (string) – The name of the option group to be used for the restored DB instance. |
|---|
| Parameters: | tags (list) – A list of tags. |
|---|
Restores a DB instance to an arbitrary point-in-time. Users can restore to any point in time before the latestRestorableTime for up to backupRetentionPeriod days. The target database is created from the source database with the same configuration as the original database except that the DB instance is created with the default DB security group.
| Parameters: | source_db_instance_identifier (string) – |
|---|
The identifier of the source DB instance from which to restore.
Constraints:
| Parameters: | target_db_instance_identifier (string) – |
|---|
The name of the new database instance to be created.
Constraints:
| Parameters: | restore_time (timestamp) – The date and time to restore from. |
|---|
Valid Values: Value must be a UTC time
Constraints:
Example: 2009-09-07T23:45:00Z
| Parameters: | use_latest_restorable_time (boolean) – Specifies whether ( True) or not ( False) the DB instance is restored from the latest backup time. |
|---|
Default: False
Constraints: Cannot be specified if RestoreTime parameter is provided.
| Parameters: | db_instance_class (string) – The compute and memory capacity of the Amazon RDS DB instance. |
|---|
Default: The same DBInstanceClass as the original DB instance.
| Parameters: | port (integer) – The port number on which the database accepts connections. |
|---|
Constraints: Value must be 1150-65535
Default: The same port as the original DB instance.
| Parameters: | availability_zone (string) – The EC2 Availability Zone that the database instance will be created in. |
|---|
Default: A random, system-chosen Availability Zone.
Example: us-east-1a
| Parameters: |
|
|---|
| Parameters: | publicly_accessible (boolean) – Specifies the accessibility options for the DB instance. A value of true specifies an Internet-facing instance with a publicly resolvable DNS name, which resolves to a public IP address. A value of false specifies an internal instance with a DNS name that resolves to a private IP address. |
|---|
| Parameters: |
|
|---|
Default: Same as source.
| Parameters: | db_name (string) – |
|---|
The database name for the restored DB instance.
This parameter is not used for the MySQL engine.
| Parameters: | engine (string) – The database engine to use for the new instance. |
|---|
Default: The same as source
Constraint: Must be compatible with the engine of the source
Example: oracle-ee
| Parameters: | iops (integer) – The amount of Provisioned IOPS (input/output operations per second) to be initially allocated for the DB instance. |
|---|
Constraints: Must be an integer greater than 1000.
| Parameters: | option_group_name (string) – The name of the option group to be used for the restored DB instance. |
|---|
| Parameters: | tags (list) – A list of tags. |
|---|
Revokes ingress from a DBSecurityGroup for previously authorized IP ranges or EC2 or VPC Security Groups. Required parameters for this API are one of CIDRIP, EC2SecurityGroupId for VPC, or (EC2SecurityGroupOwnerId and either EC2SecurityGroupName or EC2SecurityGroupId).
| Parameters: |
|
|---|


Our idea library is a work in progress and currently includes two product lines, the Modern Design Collection and the Iron Works Collection. All of our designs are fully customizable and each design can be used in double or single door configurations, with or without sidelights and transoms. Additionally, we are able to build almost any design using solid hardwood, glass, and wrought iron elements. Contact us today for all your custom door needs.


Preferred Size:
XXS
XS
S
M
L
XL
Preferred Site:
US Site
Worldwide Site
Currently Selected Items:
Save


| 1 | package fr.sii.ogham.spring.v3.template.thymeleaf; | |
| 2 | ||
| 3 | import java.util.Map; | |
| 4 | ||
| 5 | import org.slf4j.Logger; | |
| 6 | import org.slf4j.LoggerFactory; | |
| 7 | import org.thymeleaf.context.AbstractContext; | |
| 8 | import org.thymeleaf.context.IContext; | |
| 9 | ||
| 10 | import fr.sii.ogham.spring.template.thymeleaf.ContextMerger; | |
| 11 | ||
| 12 | /** | |
| 13 | * Add additional variables to an existing Thymeleaf context. It only works if | |
| 14 | * the {@link IContext} instance extends {@link AbstractContext}. | |
| 15 | * | |
| 16 | * It updates the original context in place returning the same instance. | |
| 17 | * | |
| 18 | * If you need to set variables on an instance that doesn't inherit from | |
| 19 | * {@link AbstractContext}, you have to provide another implementation. | |
| 20 | * | |
| 21 | * @author Aurélien Baudet | |
| 22 | * | |
| 23 | */ | |
| 24 | public class UpdateCurrentContextMerger implements ContextMerger { | |
| 25 | private static final Logger LOG = LoggerFactory.getLogger(UpdateCurrentContextMerger.class); | |
| 26 | ||
| 27 | @Override | |
| 28 | public IContext mergeVariables(IContext base, Map<String, Object> additionalVariables) { | |
| 29 |
1
1. mergeVariables : negated conditional → KILLED |
if (base instanceof AbstractContext) { |
| 30 |
1
1. mergeVariables : removed call to org/thymeleaf/context/AbstractContext::setVariables → KILLED |
((AbstractContext) base).setVariables(additionalVariables); |
| 31 | } else { | |
| 32 | LOG.debug("Not an AbstractContext => skip additional variables"); | |
| 33 | } | |
| 34 |
1
1. mergeVariables : replaced return value with null for fr/sii/ogham/spring/v3/template/thymeleaf/UpdateCurrentContextMerger::mergeVariables → KILLED |
return base; |
| 35 | } | |
| 36 | ||
| 37 | @Override | |
| 38 | public IContext merge(IContext base, IContext other) { | |
| 39 | for (String variableName : other.getVariableNames()) { | |
| 40 |
1
1. merge : negated conditional → KILLED |
if (base instanceof AbstractContext) { |
| 41 |
1
1. merge : removed call to org/thymeleaf/context/AbstractContext::setVariable → KILLED |
((AbstractContext) base).setVariable(variableName, other.getVariable(variableName)); |
| 42 | } else { | |
| 43 | LOG.debug("Not an AbstractContext => skip additional variables"); | |
| 44 | } | |
| 45 | } | |
| 46 |
1
1. merge : replaced return value with null for fr/sii/ogham/spring/v3/template/thymeleaf/UpdateCurrentContextMerger::merge → KILLED |
return base; |
| 47 | } | |
| 48 | } | |
Mutations | ||
| 29 |
1.1 |
|
| 30 |
1.1 |
|
| 34 |
1.1 |
|
| 40 |
1.1 |
|
| 41 |
1.1 |
|
| 46 |
1.1 |


PRIVACY POLICY
1. Overview
This Privacy Policy explains how The Mercer Club, Inc. (“The Mercer Club”, “we”, or “us”) collects,
protects, uses and shares information about you when you use themercerclubnyc.com (“Website”), our mobile
applications (“App”), and any of our services (collectively, the “Services”), and whether you access the
Services directly or through a third party.
Please understand that, except as specifically
described below, this Privacy Policy does not apply to information collected by third parties, such as other
companies, or third-party websites or mobile applications, even if any are linked to or accessible through
the Services. If you have any questions or concerns about our information practices, please contact us at
<EMAIL_ADDRESS>If you do not want information about you to be used as described
in this Privacy Policy, you must stop, or refrain from, using the Services.
2. Information We Collect
“Personal Information,” as used in this Privacy Policy, is information that directly identifies an individual,
such as a person’s name, or information that reasonably allows an individual to be identified indirectly, such
as email or home address or a person’s mobile phone number. Personal Information also includes
information that is directly combined with such identifying information.
Most of the Personal
Information we collect is from our customers. This information falls into two (2) general categories:
Passive Data Collection. This refers to data automatically collected from customers when they
visit the Website or use the Services.
User-Submitted Information. This refers to information that
customers actively submit to us, which may be provided voluntarily or as required to use our Services.
Customers also sometimes provide us with information about other individuals, such as when a customer sends a
gift card or uses our referral services to tell a friend about us. In those cases, we may ask that customer to
provide the recipient’s name and email address. (We may also collect Personal Information in any personalized
message that is submitted with a gift card or referral.) We will automatically send the recipient email
correspondence with the gift card or referral, and invite them to visit the Website or otherwise use the
Services. If we receive Personal Information for a referral or gift card, we use that information for the sole
purpose of sending this email correspondence, and for tracking the use of the gift card or the success of our
referral program.
Mobile Device Information
When you download or use our App, we receive information about your mobile device. We register your device,
and we may use the identifier to send you push notifications about your transactions via the Services.
Log Files
Like most websites, we automatically receive and record certain information about our customers’ behavior
on our Website or App and when using our Services. Our servers automatically gather technical information
about our Website or App traffic and store it in log files. This information includes Internet protocol (IP)
addresses, browser type, Internet service provider (ISP), referring/exit pages, operating system, date/time
stamp, and other clickstream data. We aggregate this information with other pieces of information to analyze
trends, to administer and improve the Services, for example to understand customers’ use of the Website and
to make inventory and purchasing decisions that will best serve our customer base. Information from log
files may also be used to determine general location information such as city, state or geographic area.
Third Party Advertisers
Third-party advertising companies may also use cookies, web beacons or similar technologies on the Website
to collect information (such as click stream information) during your visits to our Website and other
websites, as well as during your use of our Services, in order to help us provide you with advertisements
about our Services that we believe are likely to be of interest to you.
User-Submitted Information
As a general matter, we may ask you for information, or retain information, that you provide to us in order
to provide our Services to you, and to better serve you and our customer base. This category of information
includes information submitted electronically, via phone, and in person through our stores. We may also
combine this information with Personal Information to provide you with customized and personalized
Services.
We collect User-Submitted Information in the following ways:
Registration
In order to use some features of the Website, App and Services, including the rental of The Mercer Club’s
inventory, you must first create an account with us and agree to the Terms of Service. To create an account,
you must provide an email address and create a password. We may also ask you for your birthday. We use the
email address you provide to contact you about the products and Services, and to begin to create a tailored
experience for you.
Orders
If you order a product from us, we request certain Personal Information from you, whether you access the
Services from our App, the Website or otherwise. You must provide contact information (including name,
shipping address, telephone number) and a payment method. We use this information for billing purposes, to
fill your orders and to communicate with you about your orders. If we have trouble processing an order, we
will use this information to contact you.
We record what you order and associate it with your
account profile. When you return an item, we may ask you for information about your experience, such as, if
you wore it and for information regarding how it fit. We record that information to better personalize our
Services for you and to improve our Services for others.
Personalization of Service
In order to improve your customer experience, we may request personal characteristics, such as your height,
bust, dress size, style and fit preferences, your birthday, and the date and occasion for your rental. We
may also ask for your feedback and rating of our products. All of this information is voluntary and helps us
improve our Services by enabling us to create a tailored experience for you and our other
customers. Although we believe that providing this information will improve the Services we can
offer to you, and your experience of the Services, we will not require you to provide it. (Also, although we
may request information about personal physical characteristics, we do not ask for uniquely identifying
biometric information.) We may also collect geolocation information from your mobile device, if
you give us permission through your mobile device to do so..
Third-Party Account Credentials
If you choose to provide us with your third-party account credentials to such services as Google or
Facebook, you understand that some content and/or Personal Information may be shared between the third-party
service and us. Any information collected by a third party-service will be used in accordance with that
third party’s privacy policy, which we encourage you to review and consider.
3. How We Use Your Information
The purposes and ways that we may use Personal Information about you are described throughout this Privacy
Policy, often in connection with the kinds of Personal Information we collect. Other uses of Personal
Information are described below.
In addition, we may use aggregate, statistical, and
deidentified data, which does not specifically identify any individuals, for any purpose.
General Uses of Your Information
We generally use the information we collect, including Personal Information about you, for the following
purposes:
To Provide Our Services. We use your Personal Information to provide our Services to you,
including:
• To present you with products, information and content through the Services,
including personalization of the Services;
• To process transactions,
including financial transactions, related to your use of the Services;
• To assist you in finding
a location to return an item, using location or geolocation information you provide to us; and
• To
respond to your questions or requests.
For Communications and Marketing
We use your Personal Information to communicate with you and provide you with information about The Mercer
Club and our marketing partners.
To Develop and Improve Our Services
We may also use your Personal Information as we work to continually improve our Services, our business and
our operations. For example, by:
• Analyzing usage or interest in certain features, or identifying items and areas of interest to our
customers.
For Compliance, Fraud Prevention and Safety
We may use your Personal Information and disclose it to law enforcement, government authorities, and
private parties as we believe necessary or appropriate to:
• Protect our, your or others’ rights, privacy, safety or property;
• Enforce the terms and conditions
that govern use of our Services, including for legal claims; and
• To prevent, identify, investigate and
deter any fraudulent, harmful, unauthorized or illegal activity.
To Comply with Law
We may use your Personal Information as we believe necessary or appropriate to comply with applicable laws,
lawful requests, and legal process.
As Described or with Your Consent
We may use your Personal Information for any other purposes that we describe at the time
we collect your Personal Information, or otherwise with your consent.
Communications from Us
We use your contact information to communicate with you about The Mercer Club and our marketing partners in
the following ways:
• To provide newsletters, marketing emails or push notifications with special promotional offers, updates and
other relevant marketing content;
• To provide announcements about the Services;
• To communicate
with you about the Services and your account, including updates about the status of your orders; and
• To
verify your identity and address for your orders and rentals.
We may communicate with you via phone, email, text messages and push notifications to your mobile device.
Standard call, message and data rates charged by your mobile carrier may apply to text messages or other
communications received on your mobile device.
Cookies, Web Beacons and Similar Technologies
A cookie is a small text file that is stored on a computer for record-keeping or tracking purposes. Web
beacons (also known as pixel tags or clear GIFs), are graphics that can record whether a person has accessed
particular content. We use these and other similar technologies on the Website and App and in connection
with our Services.
Cookies we utilize may include session cookies, persistent cookies, or similar
technologies. A session cookie expires when you close your browser. A persistent cookie is stored on your
computer or device for an extended period of time. You can remove persistent cookies by following the
directions provided in your Internet browser's "help" menu. You may also configure your browser
to prevent cookies from being set on your computer. (Instructions should be provided in documentation for
your browser.) If you reject cookies, your ability to use the Website, App and Services may be limited, and
you may not be able to use certain features of the Website, App or Services. We may use cookies for the
following purposes.
Essential cookies. Essential cookies are required for providing you with features or services that you
have requested. For example, certain cookies enable you to log into secure areas of our Services. Disabling
these cookies may make certain features and services unavailable.
Functional cookies. Functional
cookies are used to record your choices and settings regarding our Services, maintain your preferences over
time and recognize you when you return to our Services. These cookies help us to personalize our content for
you, greet you by name, and remember your preferences (for example, your choice of language or region).
Performance/analytical
cookies. Performance/analytical cookies allow us to understand how visitors use our Services such as by
collecting information about the number of visitors to the Services, what pages visitors view on our
Services and how long visitors are viewing pages on the Services. Performance/analytical cookies also help
us measure the performance of our advertising campaigns in order to help us improve our campaigns and the
Services’ content for those who engage with our advertising.
To find out more information about
cookies, including information about how to manage and delete cookies, please
visit https://www.allaboutcookies.org/.
We may use web beacons or similar
technologies, which help manage content on the Website and in the Services by tracking what content is
effective. These technologies may be used to track the online movements of customers, but in contrast to
cookies, which are stored on a computer hard drive, these technologies are embedded in the Website or
App.
We may also use web beacons in our HTML-based emails to let us know which emails recipients have
opened. This allows us to gauge the effectiveness of certain communications and the effectiveness of our
marketing campaigns.
Surveys or Contests
We may provide you the opportunity to participate
in surveys or contests on our Website or in connection with our Services. If you participate, we
will request certain Personal Information. The requested information typically includes contact information
(such as name and email address) and demographic information.
We may use this information to
notify contest winners and to award prizes, to monitor traffic to our Services, to improve the Services, and
to send participants an email newsletter.
Additional information practices (and terms and
conditions) may apply to any survey or contest, which will be made available with the survey or contest.
Please carefully review any additional information provided.
Public Feedback and Discussion
Boards
If you choose to post messages to public message areas or leave feedback for others, that
information may become available to anyone. We are not responsible for the use by others of the information
you publicly disclose. Additionally, we may, but are not obligated to, collect the information you post in
public message areas to resolve disputes, provide customer support and troubleshoot problems as permitted by
law.
Please be careful and closely consider disclosing any Personal Information in public
message areas.
We may disclose aggregate, statistical, and deidentified data, which does not specifically identify any
individuals, for any purpose.
We may also share Personal Information about you, in general:
4. How We Disclose Your Information
• As necessary to provide the Services;
• With service providers;
• With our corporate affiliates
and business partners; and
• For legal reasons or as required by law.
The purposes and ways that we may share Personal Information about you are described below in more detail.
The Mercer Club Partners
The Mercer Club engages in marketing and promotional activities with carefully screened brands, or,
“Partners,” which we think will appeal to our customer base. From time to time, Partners may also be
provided with non-personally-identifying or aggregate information demographic information of customers on
our Services and statistical information about buying behavior, and Partners may be given opportunities to
market to select segments of our customer base indirectly. When we share aggregate or non-personally
identifiable customer data, we do so in a way that we believe cannot reasonably be linked with a customer’s
Personal Information.
Service Providers
We may provide Personal Information to third parties for use in performing research and business
functions (e.g., mailing, maintenance, security, data analytics, communications, CRM, database management
services, credit card payment processing or data hosting) on our behalf. These service providers agree to
use your Personal Information only in accordance with our instructions, with information used only as
described in this Privacy Policy and for no other purpose than to provide the contracted-for services.
Corporate Affiliate Parties
We may share some or all of your Personal Information with our affiliates (including a parent company,
subsidiaries, joint venture partners or other companies that we control or that are under common control
with us), in which case we will seek to require those affiliates to honor this Privacy Policy.
As Required by Law
We may disclose Personal Information if we have a good-faith belief that doing so is required under
applicable law, for example if we receive a subpoena or other judicial or administrative order or otherwise
required by law. This may include responding to legal requests from jurisdictions outside of the United
States, where we have a good faith belief that the response is required by law in that jurisdiction.
In Connection with Business Transactions
We may disclose Personal Information in certain corporate transactions, such as in connection with an
actual or proposed merger, acquisition, or other sale of or transfer of all or part of our business or
assets, including as part of a bankruptcy, liquidation, or other insolvency proceeding.
In
the event of a change in ownership of The Mercer Club, or a merger with, acquisition by, or transfer or sale
of all or a portion of our assets to another entity, we reserve the right to transfer all of your Personal
Information, including email addresses and other information about you collected by us (in accordance with
this policy), to that entity.
To Protect Rights
Additionally, we may disclose Personal Information where we, in good faith, deem it appropriate or
necessary to prevent violation of the Terms of Service or our other agreements; take precautions against
liability; protect the rights, property, or safety of The Mercer Club, any individual, or the general
public; maintain and protect the security and integrity of our Services or infrastructure; protect ourselves
and our Services from fraudulent, abusive, or unlawful uses; investigate and defend ourselves against
third-party claims or allegations; or assist government enforcement agencies.
5. Third Party Websites
In the event that that we provide links to other websites that we do not control, whether or not those
other websites refer to our branding, this Privacy Policy does not apply to those other websites. Visitors
to those websites are advised to carefully read the policies on those individual websites.
6. Your Choices
Accessing and Requesting Changes to Your Personal Information
If you are a customer of The Mercer
Club, you may review and change your Personal Information through your customer account.
If
you do not have a customer account with The Mercer Club, or if you cannot access or change any of your
Personal Information through your account, but you still wish to inquire about, access, correct, update or
delete Personal Information that we may hold about you, please email us
at<EMAIL_ADDRESS>Please understand that, before responding to your request, we
may ask you for additional information in order to verify your identity, or take other actions that we
believe are appropriate in order to verify your identity.
Please also understand that we may not be
obligated or able to alter or delete your Personal Information and may retain information to provide you
with requested services or fulfill obligations to you, for security reasons, if we are required under
applicable law or regulations, for internal business use or for other valid reasons. We are also not
obligated to comply with requests that are unreasonably burdensome or expensive, or with requests that would
interfere with the rights of another individual. In some circumstances, we may charge a
reasonable fee to fulfill your request.
Communications Preferences
If you would like to change the types of communications you receive from us or how you receive
communications from us, or if you would like to opt out of promotional communications, you may do so at any
time by updating the communication preferences provided in your customer account.
If you do not have a
customer account, you may also use the unsubscribe links and instructions that will be present in any
promotional emails or other communications that we send.
Please understand that, even if you opt out
of marketing or promotional communications, we may continue to send non-promotional communications such as
confirmations of transactions, changes to the Services or other information about your use of the
Services.
“Do Not Track” Settings
Our Website and Services are not at this time configured to read or respond to “do not track” settings or
signals in your browser headings.
Tailored Advertisements and Passive Data Collection
The Mercer Club also partners with advertising companies to place our advertising on third-party websites
that we believe will be of interest to you. As described elsewhere in this Privacy Policy, these advertising
companies may collect information about your visits to our Website using cookies, web beacons and similar
technologies, and these advertising companies may collect information over time and across other websites.
In using tailored advertising, we comply with the Network Advertising Initiative (“NAI”) self-regulatory
2018 Code of Conduct, Digital Advertising Alliance (“DAA”) Self-Regulatory Principles for Online Behavioral
Advertising (“OBA Principles”).
To make choices about Interest-Based Ads from participating
third parties, including to opt out of receiving behaviorally targeted advertisements from participating
organizations, please visit the DAA’s or NAI’s consumer opt out pages, which are located
at https://www.networkadvertising.org/choices/, https://optout.networkadvertising.org/
or https://www.aboutads.info/choices/.
You may also learn more about your
choices with respect to data collection by third parties, including about opting out or changing your
preferences, at those third parties’ websites. For Google, please
see www.google.com/privacy_ads.html, or you may have the option to opt out of Google's use of
cookies using the Google Analytics Opt-out Browser Add-on
at https://tools.google.com/dlpage/gaoptout/. Information about Facebook advertising may be
available at https://www.facebook.com/help/568137493302217.
7. Security
We use reasonable security measures to protect against the loss, unauthorized access, misuse, alteration
and destruction of Personal Information under our control, both during the transmission and once we receive
it.
Although we make good faith efforts to maintain the security of such Personal Information,
no method of transmission over the Internet or method of electronic data storage is 100% secure, and we
cannot guarantee that the information will remain free from unauthorized access, use, disclosure, or
alteration. While we work hard to ensure the integrity and security of our network and systems, we cannot
guarantee that our security measures will prevent hackers or other unauthorized persons from illegally
accessing or obtaining this information.
8. Children’s Privacy
The Mercer Club and the Services are not intended for or directed toward children under 13 years of
age, and children should not use the Services for any purpose unless they have the consent of, and are under
the supervision of, a parent or guardian. We ask that individuals do not provide Personal Information
through our Website or Services, and if we learn that we have collected or received Personal Information
from a child under 13 years of age, we will delete that information
Additionally, we may collect
Personal Information from teenagers between the ages of 13 and 18, but only if such an individual is of
legal age to enter into a binding contract under applicable law, or with the consent and supervision of a
parent or legal guardians, as permitted by law.
If you are the parent or legal guardian of a child under 13 years of age who has registered on the Website
or App or you believe has otherwise provided Personal Information to The Mercer Club, please contact The
Mercer Club at<EMAIL_ADDRESS>to have the account terminated and information deleted.
If
you believe that we may have inadvertently collected any Personal Information about a child aged 13 years or
younger, please contact us at<EMAIL_ADDRESS>or as provided in the “Contact Us” section
below.
9. Notices to California Residents
If you are a resident of the state of California, California’s “Shine the Light” law permits you to request
information regarding the disclosure of your Personal Information by us to a third party for the third
party's direct marketing purposes. To make such a request, please send an email to
<EMAIL_ADDRESS>In accordance with the California Consumer Privacy Act of 2018
(“CCPA”), please see the following summary of Personal Information that we have collected in the past twelve
(12) months (preceding the effective date of this Privacy Policy), as well as the sources of that Personal
Information, the purposes of collection, and third parties with who we have shared such Personal Information
in the past twelve (12) months.
In addition, we may use or disclose any Personal
Information that we collect as necessary to comply with applicable law or legal obligations as described in
this Privacy Policy.
Sale of Personal Information. We do not “sell” your Personal Information, as
defined under the CCPA, and we have not sold your Personal Information in the past twelve (12) months
(preceding the effective date of this Privacy Policy).
California Residents’ Rights under the
CCPA. Under the CCPA, California residents have certain rights regarding their Personal
Information. Subject to certain exceptions, California residents have or may exercise the
following rights:
Right to Request Deletion of Personal Information. A California resident may request that a business delete
their Personal Information.
Right to Opt-Out of the Sale of Personal Information. A California
resident has the right to opt-out of the sale of their Personal Information by a business.
Right to
Non-Discrimination for Exercise of Consumer Privacy Rights. A California resident has the right not to receive
discriminatory treatment by a business for the exercise of privacy rights provided by the CCPA.
To
submit requests to The Mercer Club to exercise these rights, California residents may use the following
methods:
1) Call us at +1<PHONE_NUMBER>
Please understand that we are only
obligated to respond to verifiable consumer requests. If we receive a request for information about
you, we need to know that it is actually coming from you, or somebody legally authorized to act for you.
We
may implement authentication procedures that are appropriate to the nature of the personal information
requested. We may also use any information that we have already collected about you in order to verify your
request. Also, if we collect any personal information to verify your request, we will only use that
information to verify your request.
Please remember that we are only obligated to respond to a
request for access twice within a 12-month period.
10. Changes to this Privacy Policy
We may change this Privacy Policy from time to time. The most recent version of the Privacy Policy will
always be posted on the Website, with the effective date posted at the top of the Privacy Policy. We may
revise and update this Privacy Policy if our practices change, as technology changes, or as we add new
services or change existing ones. If we make material changes to our Privacy Policy or how we handle your
Personal Information, or if we are going to use any Personal Information in a manner that is materially
different from that stated in our Privacy Policy at the time we collected such information, we will try to
notify you of such changes reasonably in advance. By using our Website or Services after the effective date,
you are deemed to consent to our then-current Privacy Policy.
11. Contact Us
If you have questions, concerns or feedback regarding this Privacy Policy or our information practices, you
can send an email to us at<EMAIL_ADDRESS>FAQ
Rental Policy
Privacy Policy
Terms & Conditions
Browse
Rental Policy
Editorial
Contact Us
<EMAIL_ADDRESS>About Us
Terms & Conditions
FAQs
Privacy Policy
Membership
Customer Service
(954) 787-0304
NEWSLETTER SIGN-UP
SIGN-UP FOR NEWSLETTER
THE MERCER CLUB


Dark theme
Hello Electron!
We are using Node.js
Chromium
and Electron
If you are having trouble getting program to detect your KeepKey, make sure that you don't have another KeepKey client running.
Information about your KeepKey
Detected: false
Firmware version:
Bootloader version:
Device label:


| DOSE: |
16 mg |
oral |
2C-I |
(powder / crystals) |
Set and sending for myself was pretty strong. Happy to be going out. First time for this substance, one of the first times for a pyschadellic in general.
Going to see some good music, etc.
Setting for participant 2 was a bit forboding -- she mentioned she had some issues she was working out in her head. This was a warning sign we ignored.
T.0 -- Both take 16 mg carefully weighed out in a capsule. We had two 5mg capsules ready if either of us turned out to be a hardhead. 5mg was WAY TOO MUCH for these terms. An extra 1mg or 2mg would have been appropriate. Read on.
T.40 -- Alerts start kicking in -- late for me. She's more talkative which is a major alert for her but she doesn't feel like she's coming up on anything.
T1.0 -- Sitting outside and talking some. I'm feeling reasonably euphoric and into sensations. I'm seeing wavering among objects with grids and lines (office building windows, pavement tiles, etc). She's not getting any of that. She takes a 5mg capsule.
T2.0 -- Kicked in nicely now. Enjoying music. Reality is only bending a little, not too bad. Some things seem extra-freaky or out of the ordinary. For example there are two groovin' japanese girls sitting on a couch by the dance floor. This looks really wrong like they don't belong there. In general parts of the world take on a significance out of the ordinary. I'm reminded of a music video done by a producer who is really obvious ('This graphic of a flower represents man's inhumanity to his fellow man blah blah'). My partner feels herself coming up on something but is having trouble describing it. It should be noted that she tends to come up slower on drugs of this type but this was really slow for her.
T2.1 -- I'm able to do some internal work and revelations about how I've been selfish in life. This is an introspective substance. I ponder taking another 5mg myself but am pretty happy where I am and a little scared of that large of a bump. In hindsight 17-18mg is the comfortable level for me.
T2.3 -- Dancing is pretty difficult. How is this possibly described as a 'rave' drug? Music is great and visuals are fun but dancing is waaay too much stimulation. Sex on this (or lots of foreplay) would be excellent and could make my head explode. My partner starts to feel a little overstimulated and asks to go outside.
T2.4 -- Change of setting kicked it into high gear.  She's happy, and smiling, but it is the nature of her personality to freak out a little bit at the loss of control. We get in the car and start driving after sitting for a bit. TERRIBLE idea. Driving (reflexes) are perfectly fine. But just like the japanese girls described earlier the road starts taking on metaphorical significance. I am TERRIFIED of going the wrong way down a one way street. Making a turn into oncoming traffic (even if it is clear) is similarly frightening forcing me to go out of my way to make a U-Turn.   She comments that 'the substance has an edge to it.'
It does not, honestly.  Set and setting people. :)
T3.0 -- Stopped the car. Parked at a meter. Called a cab. Cab ride was a tough one because the driver was completely insane (not the chemical speaking on this one). Getting home was such a relief.
T3.2 -- Bundled my partner up on the couch. She comments: 'I am still climbing, I haven't plateued.' 'Is this a ++++? I feel like I am +3.9 and not letting it be a ++++' and she makes some fundamentally important comments about how her mind and soul work which are too personal for this report.
I'm back in a pleasant mindset and enjoying myself and go into 'trip sitter' mode making her as comfortable as possible and helping her visualize. She is highly introverted at this point and makes little to no comments.
t6.0 -- About now she emerges. Classic 'hard trip' in that she knows it was good that it happened but doesn't need that to happen again.
 Another mistake. For christ sake, don't drive on this. Again, your physical coordination are there (unlike alchohol) which is what makes you think you are OK. But she saw a police car and fundamentally freaked out. Just like 1-way streets for me, it took on an almost other-worldly significance which is paralyzing (and thus incredibly dangeous when driving). In hindsight I would have forced her to stay or sleep over until she was completely down no matter how much she wanted her warm bed :)
Conclusion: At my level, recreationally, a pretty fun substance. I can't state enough that I enjoyed myself and figured out some good things.
At her level, which I would catagorize as heroic, it is no doubt a healer and introspective device which will be an ally if your focus is there. Be careful out there.
I hesitated to mention the driving so much in this report, but the fundamental 'significance' of ideas when driving was really a startling glimpse into how the mind works, and makes for an interesting report IMO.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.