Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
IN THE HIGH COURT OF JUDICATURE AT MADRAS Dated:01.08.2017 Coram THE HONOURABLE Mr. JUSTICE M.VENUGOPAL AND THE HONOURABLE Mr. JUSTICE P.D.AUDIKESAVALU W.P.No.214 of 2003 and WPMP 235 of 2003 ST CMS Co., Environmental & Affected Welfares Associations, Rep. By its Secretary, Dr.Govindhasamy Uthangal Village and Post, Vridhachalam .. Petitioner Vs. 1. The Chairman, Tamilnadu Pollution Control Board, Madras 32 2. The District Environmental Engineer, Tamilnadu Pollution Control Board, Cuddalore 3. The District Collector, Cuddalore 4. The Chairman & Manging Director, Neyveli Lignite Corporation, Neyveli, Cuddalore District 5. M/s ST-CMS Electric Company, Uthangal Village, Virudhachalam Taluk, Cuddalore District ..Respondents Prayer: Writ Petition filed under Article 226 of the Constitution of India praying for issuance of Writ of Mandamus in directing the 1st Respondent to revoke the Consent Order no.1194 dated 02.06.14998 given to 5th Respondent under Section 25 of the T.N.Water (Prevention and Control of Pollution) Act of 1974 and Consent Order No.1145 for clearing Air Pollution and further direct the 5th respondent to decommission his Thermal Power Project at Uthangal Village, Virudhachalm Taluk. For Petitioner : Mr.V.Raghavachari For Respondents : Mrs.Rita Chandrasekaran for R1 and R2 Mr.M.Elumalai for R3 Government Advocate Mr.Nithyanandam for R4 Mr.Arun Anbumani for R5 O R D E R
[Order of the Court was made by M.VENUGOPAL, J.] Heard both sides. The main Writ Petition itself is taken up for final disposal by consent of the parties.
2. As against the Order of Consent given to the 1st Respondent vide Consent No.1194 dated 02.06.1998 granted under Section 25 of Tamilnadu Water (Prevention and Control of Pollution) Act of 1974 and Consent Order No.1145 for clearing Air Pollution etc., the Petitioner, as per Section 31 of the Air (Prevention and Control of Pollution Act) 1981 is having an effective, efficacious, viable and alternative remedy to prefer an Appeal before the Appellate Authority/ Pollution Control Board, Chennai.
3. It comes to be known that as on date, the Consent, which was renewed from time to time, lastly renewed on 17.07.2017, which is valid up to 31.03.2020.
4. In view of the fact that the Petitioner has an effective and viable remedy of preferring an Appeal as stated supra as per Section 31 of the Air (Prevention and Control of Pollution Act) 1981 and furthermore, even after expiry of period of limitation, namely, 30 days to prefer an Appeal before the Appellate Authority, the Appellate Authority, in law if sufficient cause is shown for not preferring an Appeal in time, then, he can condone the same to secure the ends of justice.
5. In view of the foregoings, it is open to the Petitioner to prefer an Appeal before the Appellate Authority / Pollution Control Board, Chennai, if it is aggrieved against the last Order of Renewal dated 17.07.2017 where it has been renewed till 31.03.2020, if it so desires / advised. If such an Appeal is filed, the Appellate Authority / Pollution Control Board, Chennai shall look into and dispose of the same by passing a reasoned speaking order on merits, of course, after providing necessary opportunity to the Petitioner and others, as expeditiously as possible by adhering to the 'Principles of Natural Justice'.
In fine, the Writ Petition is disposed of. There shall be no order as to costs. Consequently, Connected Miscellaneous Petition is closed.
(M.V., J.) (P.D.A., J.) 01.08.2017 Index :Yes / No Internet :Yes / No Speaking order ssd To 1. The Chairman, Tamilnadu Pollution Control Board, Madras 32 2. The District Environmental Engineer, Tamilnadu Pollution Control Board, Cuddalore 3. The District Collector, Cuddalore 4. The Chairman & Manging Director, Neyveli Lignite Corporation, Neyveli, Cuddalore District 5. M/s ST-CMS Electric Company, Uthangal Village, Virudhachalam Taluk, Cuddalore District M.VENUGOPAL, J. and P.D.AUDIKESAVALU, J. ssd W.P.No.214 of 2003 and WPMP 235 of 2003 01.08.2017


@Override fun onTaskCompletedCDERiverLine(): void
Displays a CDEPoint river line returned by CDERiverLineAPI on top of the catchment GeoJsonFeature
result
- CDEPoint containing a river line obtained from an API call in CDERiverLineAPI
See Also
CDERiverLineAPI


--- layout: post title: It’s All About The Benjamins, when the emphasis is on the Employees and the Customers they serve. InFocus Weekly Roundup – March 9, 2012 date: '2012-03-09T14:13:04-08:00' tags: tumblr_url: http://alexhwilliams.tumblr.com/post/19020064429/its-all-about-the-benjamins-when-the-emphasis-is-on ---


I used versed when I was having some rough times in school (med school believe it or not) & thought I was going to harm myself if I didn't find a short vacation from stress. The alcohol wasn't helping anymore. This drug is fantastic for helping me relax, to stop obsessing, to sleep restfully... Wonderful.
BUT!!! It has some bad sides too. Too much can make you stop breathing. You sleep SO soundly that you could easily vomit and choke to death. I awoke one night with dried vomit in my mouth. I don't know why I didn't die, but I did end up with a bad pnuemonia a week or so later as the consequence of inhaling stomach acid & food.
Versed is easily a truth serum. It makes me willing to tell ANYONE ANYTHING. I wouldn't remember a lot of things I said and did the next day. Or I wouldn't be sure if I dreamed those things or they actually happened. The sensation of lost time can be unnerving. Finally, it's relatively expensive.
It also causes extreme uncoordination although this is not entirely unpleasant really! I didn't have any trippy, weird experiences, just plain old relaxation & a temporary escape from reality.
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.


DLSU STUDENT INFORMATION SYSTEM
Please follow the directions sent to your email to reset your password.


Marcus is fascinated by technology. He loves learning new things. He is a Software Engineer at Bosch and has a personal blog at MarcusEisele.com.


Read Gordon Sondland's explosive opening statement at the impeachment hearing
by NBC News
Opening Statement of Ambassador Gordon D Sondland (November 20, 2019) (PDF)
Opening Statement of Ambassador Gordon D Sondland (November 20, 2019) (Text)


Back to Map
Look for: Awl-shaped bluish-green needles 1/8-1/2 inches in length
Origin: California, USA
Giant Sequoia is the world’s largest tree in terms of total volume. In the Sierra Nevada Mountains of California these beasts can grow to heights of more than 275 feet and have trunk diameters exceeding 25 feet. Furthermore, they can live to be over 3,000 years old. On the east coast of the U. S. trees reach heights of 60-100 feet tall. “Big Trees” as they are often called, are at the edge of their cold hardiness in Connecticut. Growth in the northeastern U. S. is limited by the fact that the ground often freezes before it snows, providing challenges for the root system. This majestic columnar evergreen has bluish green needles that vary in length with 1 and 1/2" to 3" reddish-brown cones. Its rich reddish-brown trunk stands out in any landscape. Grows in many different soils, and requires full sun.
Early loggers are said to have destroyed hundreds of ancient sequoias in search of wood for roof shingles, flumes, fence posts and poles. But sequoia wood lacks strength and breaks easily across the grain. When they would fell these massive trees, large portions of the trunk would shatter into thousands of short, jagged and worthless shards. Other portions of the tree were left behind because they were simply too large to haul out of the forest.
USDA Zones 6-8


@include('./partials/head.html')
@include('./partials/svg-icons.html')
@include('./partials/sidebar.html')
@include('./partials/header.html')
Edit
Open
Sign
Share
10
20
50
75
100
@include('./elements/table.html')


The homepage of a dataset listing displays everything that you need to get started using the dataset. The following table describes the tabs on the homepage:
| Tab | Description |
|---|---|
| About | High-level overview of the dataset and the data provider |
| Documentation | Instructions on using the dataset in backtests and the Research Environment |
| Research | A demonstration research notebook of analyzing the dataset |
| Examples | Full example algorithms that use the dataset |
| Licenses | A list of licenses available for the dataset |
| CLI | Command generator to download the dataset with the CLI |
| Pricing | The price to access the dataset in the cloud or on your local machine |
| Data Explorer | A table to inspect the dataset files and report data issues |
The following table describes the sections displayed under the About tab for most datasets:
| Tab | Description |
|---|---|
| Introduction | High-level overview of what the dataset includes, who it's created by, and how it's created. |
| About the Provider | Description of the data provider and a link to their website. |
| Getting Started | The line(s) of code that you need to use the dataset in algorithms. |
| Data Summary | A table that displays the dataset's start date, coverage, resolution, density, and timezone. |
| Example Applications | A list of ideas on using the dataset in your algorithm. |
| Data Point Attributes | A set of widgets that display the factors in the dataset, the class members of objects that you use when accessing the dataset, and enumeration values that you can use to customize the dataset. |
| Pricing | The price to access the dataset in the cloud or on your local machine. |
| Reviews | Reviews from members who have purchased the dataset. |


/* This file is part of Ext JS 4 Copyright (c) 2011 Sencha Inc Contact: http://www.sencha.com/contact Commercial Usage Licensees holding valid commercial licenses may use this file in accordance with the Commercial Software License Agreement provided with the Software or, alternatively, in accordance with the terms contained in a written agreement between you and Sencha. If you are unsure which license is appropriate for your use, please contact the sales department at http://www.sencha.com/contact. */ /** * A specialized container representing the viewable application area (the browser viewport). * * The Viewport renders itself to the document body, and automatically sizes itself to the size of * the browser viewport and manages window resizing. There may only be one Viewport created * in a page. * * Like any {@link Ext.container.Container Container}, a Viewport will only perform sizing and positioning * on its child Components if you configure it with a {@link #layout}. * * A Common layout used with Viewports is {@link Ext.layout.container.Border border layout}, but if the * required layout is simpler, a different layout should be chosen. * * For example, to simply make a single child item occupy all available space, use * {@link Ext.layout.container.Fit fit layout}. * * To display one "active" item at full size from a choice of several child items, use * {@link Ext.layout.container.Card card layout}. * * Inner layouts are available by virtue of the fact that all {@link Ext.panel.Panel Panel}s * added to the Viewport, either through its {@link #items}, or through the items, or the {@link #add} * method of any of its child Panels may themselves have a layout. * * The Viewport does not provide scrolling, so child Panels within the Viewport should provide * for scrolling if needed using the {@link #autoScroll} config. * * An example showing a classic application border layout: * * @example * Ext.create('Ext.container.Viewport', { * layout: 'border', * items: [{ * region: 'north', * html: '
Page Title
', * autoHeight: true, * border: false, * margins: '0 0 5 0' * }, { * region: 'west', * collapsible: true, * title: 'Navigation', * width: 150 * // could use a TreePanel or AccordionLayout for navigational items * }, { * region: 'south', * title: 'South Panel', * collapsible: true, * html: 'Information goes here', * split: true, * height: 100, * minHeight: 100 * }, { * region: 'east', * title: 'East Panel', * collapsible: true, * split: true, * width: 150 * }, { * region: 'center', * xtype: 'tabpanel', // TabPanel itself has no title * activeTab: 0, // First tab active by default * items: { * title: 'Default Tab', * html: 'The first tab\'s content. Others may be added dynamically' * } * }] * }); */ Ext.define('Ext.container.Viewport', { extend: 'Ext.container.Container', alias: 'widget.viewport', requires: ['Ext.EventManager'], alternateClassName: 'Ext.Viewport', // Privatize config options which, if used, would interfere with the // correct operation of the Viewport as the sole manager of the // layout of the document body. /** * @cfg {String/HTMLElement/Ext.Element} applyTo * Not applicable. */ /** * @cfg {Boolean} allowDomMove * Not applicable. */ /** * @cfg {Boolean} hideParent * Not applicable. */ /** * @cfg {String/HTMLElement/Ext.Element} renderTo * Not applicable. Always renders to document body. */ /** * @cfg {Boolean} hideParent * Not applicable. */ /** * @cfg {Number} height * Not applicable. Sets itself to viewport width. */ /** * @cfg {Number} width * Not applicable. Sets itself to viewport height. */ /** * @cfg {Boolean} autoHeight * Not applicable. */ /** * @cfg {Boolean} autoWidth * Not applicable. */ /** * @cfg {Boolean} deferHeight * Not applicable. */ /** * @cfg {Boolean} monitorResize * Not applicable. */ isViewport: true, ariaRole: 'application', initComponent : function() { var me = this, html = Ext.fly(document.body.parentNode), el; me.callParent(arguments); html.addCls(Ext.baseCSSPrefix + 'viewport'); if (me.autoScroll) { html.setStyle('overflow', 'auto'); } me.el = el = Ext.getBody(); el.setHeight = Ext.emptyFn; el.setWidth = Ext.emptyFn; el.setSize = Ext.emptyFn; el.dom.scroll = 'no'; me.allowDomMove = false; Ext.EventManager.onWindowResize(me.fireResize, me); me.renderTo = me.el; me.width = Ext.Element.getViewportWidth(); me.height = Ext.Element.getViewportHeight(); }, fireResize : function(w, h){ // setSize is the single entry point to layouts this.setSize(w, h); } });


Dashboard
Set Batch
Expire Batch
Approve Researchers
Promote Researchers
Send Notice
Register Supervisors
Register Special Users
Edit Users
Block Users
Remove Users
View Scholars
View Supervisors
View Co-Supervisors
View Authorities


Web Developer, who uses both logic and empathy to solve everyday problems. Analytically approaches challenges with vigor and a methodic mind. Ability to exert calm and patience during stressful situations while remaining focused on the tasks at hand. Dedicated to collaborating and learning from others.
Front-end Development
JavaScript, jQuery, Backbone.js, Jasmine, JSON, AJAX, CSS, HTML
Back-end Development
Ruby, Ruby on Rails, Rspec, Pstgres SQL


There are a variety of other firstByte workshops that will be about web Development throughout the weekend. Covering topics including: JavaScript, Node.js, Bootstrap, and others! We hope to see you at those as well!
Project 1
Project 2
Project 3
Project 4
Project 5
Project 6


The Jorai keyboard was designed for the Jorai (or Jarai) language of Viet Nam.
The Jorai keyboard layout is documented in this file: welcome.htm.


Overview
NLPCraft 0.7.0 brings about several important features:
-
The project has moved to JDK 11 Java version and therefore is no longer compatible with previous
versions or prior JDK version.
-
We introduced @NCIntentSample annotation
that is broadly used throughout the project:
- In model auto-validation.
- In the new synonym suggestion tool.
- In the upcoming BERT-based server side enricher.
-
We introduced model auto-validation based on @NCIntentSample annotation
that allows for zero-code testing of the models (all shipped examples have been updated accordingly).
-
We introduced synonym suggestion tool that takes an existing model, analyses its synonyms and intents and comes up
with a list of synonyms that are currently missing that you might want to add to your model.
-
We've added a preview of the upcoming REPL tool for NLPCraft (see
nlpcraft.{shg|cmd}
scripts in the bin folder)
and corresponding ASCI/ANSI support for both server and probe log output.


{% extends "images_api/index.html" %} {% block maincontent %}
Thanks for spending some quality time with us today. Go Home


I'm from Colorado. I spent most of my childhood in Fort Morgan and was raised by grandparents and various family members. Fort Morgan is out on the Great Plains and there isn't much there. I learned to entertain myself, appreciate small details, and solitude. I cared for my sick grandmother until she died when I was 12. Childhood.
I went to CU since Boulder seemed like a "liberal" place in Colorado and therefore very different from my hometown but still instate tuition. I graduated with my BFA in 2013. Highlights: I took gaurdianship of my sister when I was 22 and she was 17. My artwork was displayed in the CU Art Museum. I was published Walkabout Creative Arts Journal. And I built a guitar.
After school I worked some different jobs. I had an internship at the DAM. I was a metal fabricator building custom work for houses in Aspen. That was fun overall but not worth destroying my body. Since that I've been a barista at Walnut Cafe. This past summer I took off work and rode my bike from Calgary, CA back to Boulder along dirt roads in the mountains.


TERMS AND CONDITIONS
Any use of this website or any of its affiliates assumes that you fully understand and agree to these Terms of Service along
with our Privacy Policy. We reserve the right to add to, delete or change the Terms and Conditions because of frequent
changes in Internet technology and applicable law. You are responsible for checking these Terms and Conditions for
changes.
I. Membership
-
You must be a resident of USA, Canada, UK, or Australia.
-
You must be at least 18 years of age or older. Individuals 16 and 17 years old can also participate, if they have parental
permission to do so, although they may not be able to complete certain offers.
-
The preferred method of payment is PayPal; You should have a Verified PayPal Account to receive payments.
-
You must register and provide your valid and complete information including legal name, email address, shipping address,
and phone number. Any changes should be updated on the site in a timely manner.
-
We may conduct a member phone number verification through an automated phone verification system which places a phone call
to the number entered and ask them to enter a randomly generated pin.
-
No P.O. Box addresses permitted, if used will have your account placed on hold until a valid address is provided. Stay assured
your details will not be shared or sold.
-
Only one account per Person / Internet Connection or IP Address / Household. Sharing or Usage of Duplicate IP Address, Multiple
Accounts Registration, and Multiple Members in one Household are strictly prohibited. If violated, account will
be placed on hold.
-
You should not sign up from or even log in from a public area such as a workplace, college campus, or library. Do not sign
up or log in to our site via a proxy, which includes ISPs such as AOL. Your account will be placed on hold if violated.
-
A registered account with our network is permanent and cannot be deleted. This helps us ensure that nobody else signs up
with the same information.
-
Accounts may be suspended, banned or put on permanent hold for rude, abusive, threatening or profane behavior.
-
Accounts may also be suspended or closed at any time if suspicious activity is found.
-
In order to ensure quality and prevent offer fraud, we reserve the right to put any account on identification hold for any
reason, without explaining the exact details of what triggered the hold. In the event of an account being placed
on identification hold, a photo of a valid government issued ID, as well as a proof of address, may be requested.
No payments will be processed for any referral level completion until an identification hold is lifted. If photos
are unreadable or suspect, we may ask for a better photo or other proof. If identity fraud is suspected, we may
ask for a photo of the user holding the ID next to their face. Any fraudulent documents sent to lift a hold will
result in account closure.
-
Usage of virtual accounts/cards, prepaid cards, gift cards, rewards cards, or any card that is not bank issued is strictly
prohibited. If usage of these cards is suspected or fraudulent transactions are suspected, proof or card and transaction
may also be asked, and account will remain on hold indefinitely until proof is provided.
-
We reserve the right to put any account on hold indefinitely for violations of our terms of service. If we suspect fraud,
false information, or any terms of service violation, we may also put any account on hold for verification purposes.
-
A sponsor/referrer will not be able to receive payment for a referral completion while that referral is on hold. If a sponsor/referrer
is on hold, they will not be able to place any orders on any referrals or receive any downline or bonus commissions
while on hold.
-
If a referral requests a transfer, we may transfer the user without consent from the current sponsor. If the referral has
completed levels before being transferred that are unpaid, we will keep record of it and allow the sponsor to cash
out on the referrals completed levels providing that neither the referral nor sponsor is on hold, that their credits
don't get revoked and that the sponsor is at the appropriate level to qualify to receive payment for the referral’s
completed levels.
-
Although Level Rewards offers a way to earn advertising commissions, it should be understood that it is not a job.
-
Sending unsolicited emails / messages to acquire referrals and posting your referral links at places where it is not welcome
is called Spamming. Spamming will not be tolerated.
-
Promoting our site or getting signups through the use of malware or deceptive redirects is strictly prohibited and will lead
to account suspension.
II. Sponsor Offers:
-
You must obtain the required amount of credits by completing offers to be counted as a referral for the person who referred
you to our Network.
-
You must signup for the offers by clicking on the link provided on the offers page. You are advised to disable popup blocks
and make sure your browser allows cookies in order to receive credit as well as clear the browser cookies and cache
before completing any offers.
-
You should not use any type of virtual accounts/cards, prepaid cards, gift cards, rewards cards, or any card that is not
bank issued to complete offers. If found, your account may be put on hold permanently.
-
We are not responsible for the Terms and Requirements for the Individual offers and are not responsible for any unknown or
unexpected charges that you receive from one or more of our offers. We strongly suggest that you read the terms
and conditions of the offer before completing it.
-
You may complete an offer only once. Completing an offer more than once will result in the credit being revoked and your
account being put on hold.
-
Credited offers can be revoked for the following reasons: 1) Not trying out the product or service after completing the offer.
2) Quick/Immediate cancellation (Not keeping trial for at least 90% of the trial period or a different length if
stated in the requirements). 3) Not abiding by the stated requirements of the offer. 4) Using false information.
5) Using a prepaid card, gift card, virtual card, lost or stolen card. 6) Using a zero balance card or account
that declines when the advertiser tries to bill it. 7) Completing an offer multiple times, whether on our network
or on any other network. 8) Any fraudulent activity done on the advertiser's site or on our site. 9) Requesting
a refund on a non-trial offer.
-
You should only complete offers that you are interested in and you should not cancel without trying the offer. Completing
an offer only to get free gifts is considered fraud and you will not receive credit for such offers, and even if
you did receive credit it will be revoked and your account will be placed on hold.
-
We reserve the right to refuse or revoke credits for offer completions. Reasons for this include but are not limited to,
duplicate offer completions, fraudulent information, the use of prepaid/virtual/gift/rewards cards, or non-payment
from the providers.
-
The amount of time taken to get credit for completing an offer varies depending on the offer completed, the advertiser, etc.
Approximate crediting times are displayed on the offer description.
-
You must save all confirmation emails received from the affiliate companies.
-
If you have completed an offer and waited the required amount of time (typically within the first 6 hours) but did not receive
the credit yet, you may place a request by going to the support section. Members may not always receive credit
for completions due to circumstances beyond our control.
We reserve the right to refuse a Missing Credit Request for any of the following reasons:
-
If the offer explicitly states that it does not accept missing credit requests.
-
If the offer was completed with invalid information.
-
If the missing credit request is filed more than 30 days after offer completion.
-
If the offer was not completed as stated in the offer description/requirements/restrictions.
-
If the member was not approved by the advertiser.
-
If the offer was completed from a public IP or duplicate IP address.
-
If the offer was not completed through our site link.
-
If the offer was previously completed on our site or any other site.
-
If the member is not a new customer.
-
If member refuses to provide proofs requested by support.
-
If the completion was fraudulent. This includes sharing cards between members during offer completion.
-
If the offer was completed using a P.O. Box address or Incomplete Address such as missing Apt #.
-
If a virtual account/card, prepaid card, gift card, rewards card, or any card that is not bank issued was used to complete
the offer.
-
Encouraging referrals to game the offers by either trying to use zero balance cards, cancelling early or any other activity
that results in low quality leads for the advertiser may result in the sponsor and the referrals accounts being
placed on hold, suspended or banned.
-
If the offer requirements were not fully met or if the offer was completed in violation of any part of our Terms of Service.
-
Early cancellation.
-
Offer credits are not transferable within member accounts.
-
No Walking Through -- A member may not walk a referral through the completion of an offer. All members must sign up for offers
based on their personal likes and dislikes themselves. If a member is believed to have walked a referral through
offer process, all involved parties will have their accounts placed on hold.
-
If an interested party has a disability that affects their ability to use our site they may receive assistance, but a support
ticket describing the situation must be created before an offer is completed.
III. Rewards:
-
Orders are processed within 24 hours upon placement. We will make all possible efforts to make sure that you receive your
payments and rewards at the earliest.
-
We will send out Bank Checks to the mailing/shipping address or PayPal account listed on your account. It is your responsibility
to update this information. We are not responsible for rewards lost due to incorrect mailing/shipping addresses
or incorrect PayPal account.
-
PayPal payments will only be sent to Verified PayPal accounts. If the PayPal account of the member is not verified the payments
will not be sent out until their account is verified.
-
We do not guarantee the availability of any reward offered on our site however we will put all human efforts to bring your
rewards to you. If the reward you required is not available at that time, we will contact you and give you all
the options available including payments in cash or check. Your reward will be processed and mailed/shipped out
at the earliest.
-
We may request for a copy of the Member's ID to verify your account when orders are placed, if you do not comply then payment
will not be sent.
-
If your rewards are valued to more than $599.00 you will be required to submit an IRS W-9 or W-8 form, this is required by
the federal law. The form should be filled in its entirety and mailed back to us at<EMAIL_ADDRESS>IV. Contact Information:
You can contact our support team by sending in an email to
<EMAIL_ADDRESS>or use our contact us page. Our user-friendly support team will respond to your requests
in a timely manner, ensuring that you receive timely responses. If you have any questions pertaining to your account
or your referrals you are advised to place a support ticket by logging into your account.


Box truck flips into home in Great Kills, Staten Island
by Eyewitness NewsGREAT KILLS, Staten Island (WABC) -- A box truck overturned into a home in the Great Kills section of Staten Island early Wednesday.
The truck flipped in the driveway of the home on Hillcrest Street just after 7 a.m.
The driver of the truck suffered injuries and was taken to a local hospital.
"We had a box truck that overturned and crashed into a private dwelling. We suspect it was a medical episode. The driver had a condition that caused him to crash into a house. He is being evaluated at a local hospital," the FDNY said. "The occupants of the house were in the house but are OK."
The house appears to have sustained minor structural damage.
"It was surreal," the homeowner said.
The Department of Buildings will check the structural stability of the residence.


This page allows you to edit or create a single access control rule.
The first section Objects being granted determines which DNs in
your database the rule will apply to. You can either select All objects
for the entire database, or Object with DN for objects matching whatever
you enter into the adjacent field.
The match type menu determines if the rule applies to just this object,
those under it, or if the DN is treated as a regular expression. You can also
further control which objects are granted by entering an LDAP filter into the
Limit with object filter field, like (objectClass=posixAccount).
The second part of the page is a table for selecting which LDAP users have
access to the objects. You can either select several general user classes from
the Grant access to menu, or choose Other and enter a specific
DN.
The Access level menu determines what these users can do with the
objects. The lower more powerful levels imply all of those above them, so a
user with Write access can also Read and Search.


Monkeys love the Modal Dialog from Bootstrap, but they're getting angry because they have to write this stuff:

<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>

Modal title

One fine body…

<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
<button type="button" class="btn btn-primary">Save changes</button>

What they want is more like this:
Like it? See Available Options or try more Examples below.
Provide only the message to show, and keep all other things default.
There are some workarounds for loading remote page into BootstrapDialog as message, one of those workarounds is as below.
Check out the remote.html.
Another solution of loading remote page into BootstrapDialog.
This one is more flexible and customizable, but it's also a bit more complicated to use.
Buttons that created by BootstrapDialog have some extra functions available:
$button.toggleEnable(true|false);
$button.enable(); // Equals to $button.toggleEnable(true);
$button.disable(); // Equals to $button.toggleEnable(false);
$button.toggleSpin(true|false);
$button.spin(); // Equals to $button.toggleSpin(true);
$button.stopSpin(); // Equals to $button.toggleSpin(false);
Try to press the keys that have been associated with buttons below.
The last button is disabled so nothing is going to happen when pressing its hotkey.
Please note that if there are some components that require keyboard operations in your dialog, conflicts may occur, you can try next example.
Try to avoid doing similar in your code.
A good looking stacked dialogs. Please also note the second and the third dialog are draggable.
BootstrapDialog.show(...) is just a shortcut method, if you need dialog instances, use 'new'.
In fact BootstrapDialog.show(...) will also return the created dialog instance.
This example demonstrates opening and closing a batch of dialogs at one time.
Dialog that created by BootstrapDialog will be in a container BootstrapDialog.dialogs before it's closed and destroyed, iterate BootstrapDialog.dialogs to find all dialogs that havn't been destroyed.
By default, the dialog size is 'size-normal' or BootstrapDialog.SIZE_NORMAL, but you can have a larger dialog by setting option 'size' to 'size-large' or BootstrapDialog.SIZE_LARGE.
Please note that specifying BootstrapDialog.SIZE_WIDE is equal to using css class 'modal-lg' on Bootstrap Modal.
BootstrapDialog supports displaying rich content, so you can even use a video clip as your message in the dialog.
If option 'closable' is set to false, the default closing behaviors will be disabled, but you can still close the dialog by using dialog.close().
By default, when option 'closable' is set to true, dialog can be closed by these ways: clicking outside the dialog, pressing ESC key, clicking the close icon on the right of dialog header.
If you want your dialog closes only when the close icon in dialog header was clicked, try setting both of the options 'closeByBackdrop' and 'closeByKeyboard' to false.
Setting option 'animate' to false to disable animation for the opening dialog.
If you want to disable animation globally, try to do this:
BootstrapDialog.configDefaultOptions({
animate: false
});
Lazy guys must love this.
When option 'draggable' is set to true, your dialog can be moved by dragging on its header.
If you would like to change the cursor shape of hovering on dialog header, you can try the following css lines:
This is useful for applying effects to specific dialogs.
For example if you would like to give your 'login-dialog' a smaller size, you can do this way:
This adds an 'aria-describedby' attribute to your dialog, which provides a description of the dialog for screen readers.
Please note that if you're going to use setters to configure event handlers, use dialog.onShow(function) and dialog.onHide(function).
Option 'onhide' gives you an opportunity to stop closing the dialog according to some conditions, making your 'onhide' callback returns false to stop closing the dialog.
In the following example, the dialog closes only when your most favorite fruit is 'banana' (Case insensitive).
All options shown below are optional.
To provide local messages for you needed, reset those messages below before using BootstrapDialog.
Please note that all options described below are optional, but you will have a weird dialog if you don't even give it a message to display.
Most options can be set via init options or property setters.
| Option | Possible values | Description |
|---|---|---|
| type |
BootstrapDialog.TYPE_DEFAULT or 'type-default' BootstrapDialog.TYPE_INFO or 'type-info' BootstrapDialog.TYPE_PRIMARY or 'type-primary' (default) BootstrapDialog.TYPE_SUCCESS or 'type-success' BootstrapDialog.TYPE_WARNING or 'type-warning' BootstrapDialog.TYPE_DANGER or 'type-danger' |
Give your dialog a specific look, color scheme can be seen on Bootstrap's Button. |
| size |
BootstrapDialog.SIZE_NORMAL or 'size-normal' (default) BootstrapDialog.SIZE_WIDE or 'size-wide' BootstrapDialog.SIZE_LARGE or 'size-large' |
- |
| cssClass | - | Additional css classes that will be added to your dialog. |
| title | String or Object(html) | - |
| message | String or Object(html) | - |
| buttonPosition | String |
header: using close section footer |
| buttons | array |
Examples:
BootstrapDialog.show({
title: 'Say-hello dialog',
message: 'Hello world!',
buttons: [{
id: 'btn-ok',
icon: 'glyphicon glyphicon-check',
label: 'OK',
cssClass: 'btn-primary',
data: {
js: 'btn-confirm',
'user-id': '3'
},
autospin: false,
action: function(dialogRef){
dialogRef.close();
}
}]
});
id: optional, if id is set, you can use dialogInstance.getButton(id) to get the button later. icon: optional, if set, the specified icon will be added to the button. cssClass: optional, additional css class to be added to the button. data: optional, object containing data attributes to be added to the button. autospin: optional, if it's true, after clicked the button a spinning icon appears. action: optional, if provided, the callback will be invoked after the button is clicked, and the dialog instance will be passed to the callback function. |
| closable | true | false |
When set to true, you can close the dialog by:
|
| spinicon |
Icon class name, for example 'glyphicon glyphicon-check'. Default value is 'glyphicon glyphicon-asterisk'. |
Specify what icon to be used as the spinning icon when button's 'autospin' is set to true. |
| data | Key-value object. For example {'id' : '100'} | Data to be bound to the dialog. |
| onshow | function |
If provided, it will be invoked when the dialog is popping up. |
| onshown | function |
If provided, it will be invoked when the dialog is popped up. |
| onhide | function |
If provided, it will be invoked when the dialog is popping down. |
| onhidden | function |
If provided, it will be invoked when the dialog is popped down. |
| autodestroy | true (default) | false | When it's true, all modal stuff will be removed from the DOM tree after the dialog is popped down, set it to false if you need your dialog (same instance) pups up and down again and again. |
| description | String | If provided, 'aria-describedby' attribute will be added to the dialog with the description string as its value. This can improve accessibility, as the description can be read by screen readers. |
| nl2br | true | false | Automatically convert line breaking character to
 if it's set to true, everything keeps original if it's false. |
| Method | Description |
|---|---|
| open() | Open the dialog. Usage: dialogInstance.open() |
| close() | Close the dialog. Usage: dialogInstance.close() |
| getModal() | Return the raw modal, equivalent to $('

') |
| getModalDialog() | Return the raw modal dialog. |
| getModalContent() | Return the raw modal content. |
| getModalHeader() | Return the raw modal header. |
| getModalBody() | Return the raw modal body. |
| getModalFooter() | Return the raw modal footer. |
| getData(key) | Get data entry according to the given key, returns null if no data entry found. |
| setData(key, value) | Bind data entry to dialog instance, value can be any types that javascript supports. |
| enableButtons(boolean) | Disable all buttons in dialog footer when it's false, enable all when it's true. |
| setClosable(boolean) | When set to true (default), dialog can be closed by clicking close icon in dialog header, or by clicking outside the dialog, or, ESC key is pressed. |
| realize() | Calling dialog.open() will automatically get this method called first, but if you want to do something on your dialog before it's shown, you can manually call dialog.realize() before calling dialog.open(). |


Symbol Index for ".Types of Agent"
Symbol Index for diagram
".Types of Agent"
AA/nature (Generalization Node)
AA/origin (Generalization Node)
ABD/party (Generalization Node)
Agent (Class)
Agent By Devolvement (Class)
Agent By Licence (Class)
Agent For First Party (Class)
Agent For Third Party (Class)
Agent/authorisation (Generalization Node)
at some specified (Association)
Authorised Agent (Class)
authority (Association)
DA/volition (Generalization Node)
Derived Agent (Class)
Derived Agent By Agreement (Class)
Derived Agent By Decree (Class)
for some (Association)
Free Agent (Class)
from (Association)
has role as (Association)
has role as (Association)
Location (Class)
origin (Association)
Principal Agent (Class)
represented (Association)
Subject (Class)
Subject Characteristic Type (Class)
Timepoint (Class)
to (Association)


认证¶
$ npm install @feathersjs/authentication --save
The [@feathersjs/authentication](https://github.com/feathersjs/authentication) module assists in using JWT for authentication. It has three primary purposes:
Setup an
/authentication
endpoint to create JSON Web Tokens (JWT). JWT are used as access tokens. You can learn more about JWT at jwt.ioProvide a consistent authentication API for all Feathers transports
Provide a framework for authentication plugins that use Passport strategies to protect endpoints.
注解
If you are using a 0.x version of
:doc:feathers-authentication
please refer to the migration guide <https://github.com/feathersjs/authentication/blob/4344c6f037f2660e4636c1c05ea22a0000649312/docs/migrating>.
The hooks that were once bundled with this module are now located at
feathers-authentication-hooks.
Complementary Plugins¶
The following plugins are complementary, but entirely optional:
Using the authentication server on the client: @feathersjs/authentication-client
Local (username/password) authentication: @feathersjs/authentication-local
JWT authentication: @feathersjs/authentication-jwt
OAuth1 authentication: @feathersjs/authentication-oauth1
OAuth2 authentication: @feathersjs/authentication-oauth2
app.configure(auth(options))¶
Configure the authentication plugin with the given options. For options that are not provided, the default options will be used.
const auth = require('@feathersjs/authentication');
// Available options are listed in the "Default Options" section
app.configure(auth(options))
重要
The plugin has to be configured before any other service.
Options¶
The following default options will be mixed in with your global auth
object from your config file. It will set the mixed options back onto
the app so that they are available at any time by calling
app.get('authentication')
. They can all be overridden and are
required by some of the authentication plugins.
{
path: '/authentication', // the authentication service path
header: 'Authorization', // the header to use when using JWT auth
entity: 'user', // the entity that will be added to the request, socket, and context.params. (ie. req.user, socket.user, context.params.user)
secret: 'supersecret', // either the secret for HMAC algorithms or the PEM encoded private key for RSA and ECDSA.
service: 'users', // the service to look up the entity
passReqToCallback: true, // whether the request object should be passed to the strategies `verify` function
session: false, // whether to use sessions
cookie: {
enabled: false, // whether cookie creation is enabled
name: 'feathers-jwt', // the cookie name
httpOnly: false, // when enabled, prevents the client from reading the cookie.
secure: true // whether cookies should only be available over HTTPS
},
jwt: {
header: { typ: 'access' }, // by default is an access token but can be any type. This is not a typo!
audience: 'https://yourdomain.com', // The resource server where the token is processed
subject: 'anonymous', // Typically the entity id associated with the JWT
issuer: 'feathers', // The issuing server, application or resource
algorithm: 'HS256', // the algorithm to use
expiresIn: '1d' // the access token expiry
}
}
注解
The typ
in the JWT header options is not a typo. It is
the typ parameter defined in the JWT
specification.
app.service(‘authentication’)¶
The heart of this plugin is a service for creating JWT. It’s a normal
Feathers service that implements only the create
and remove
methods. The /authentication
service provides all of the
functionality that the /auth/local
and /auth/token
endpoints
did. To choose a strategy, the client must pass the strategy
name in
the request body. This will be different based on the plugin used. See
the documentation for the plugins listed at the top of this page for
more information.
service.create(data)¶
The create
method will be used in nearly every Feathers application.
It creates a JWT based on the jwt
options configured on the plugin.
The API of this method utilizes the context
object.
If you are manually generating JWT’s, and for example, wanted to create
a JWT with the payload {userId: "abc123"}
:
const data = {payload: {userId: "abc123"}};
service.create(data);
Anything included in the data.payload
object will be in the JWT’s
payload. If you include a payload
object in
params,
it’s properties will take precedence over data
.
service.remove(data)¶
The remove
method is used less often. Its main purpose is adding
hooks to the “logout” process. For example, in services that require
high control over security, a developer can register hooks on the
remove
method that perform token blacklisting.
service.hooks({ before })¶
These properties can be modified to change the behavior of the
/authentication
service:
context.data.payload {Object}
- determines the payload of the JWTcontext.params.payload {Object}
- also determines the payload of the JWT. Any matching attributes in thecontext.data.payload
will be overwritten by these. Persists into after hooks.context.params.authenticated {Boolean}
- After successful authentication, will be set totrue
, unless it’s set tofalse
in a before hook. If you set it tofalse
in a before hook, it will prevent the websocket from being flagged as authenticated. Persists into after hooks.
service.hooks({ after })¶
context.params[entity] {Object}
- After successful authentication, theentity
looked up from the database will be populated here. (The default option isuser
.)
app.passport¶
app.passport.createJWT(payload, options)¶
app.passport.createJWT(payload, options) -> Promise
is used by the
authentication service to generate JSON
Web Tokens.
payload {Object}
- becomes the JWT payload. Will also include anexp
property denoting the expiry timestamp.options {Object}
- the options passed to jsonwebtoken sign()secret {String | Buffer}
- either the secret for HMAC algorithms, or the PEM encoded private key for RSA and ECDSA.jwt
- See the jsonwebtoken package docs for other available options. The authenticate method uses the default ``jwt` options <#default-options>`_. When using this package directly, they have to be passed in manually.
The returned promise
resolves with the JWT or fails with an error.
app.passport.verifyJWT(token, options)¶
Verifies the signature and payload of the passed in JWT token
using the options
.
token {JWT}
- the JWT to be verified.options {Object}
the options passed to jsonwebtoken verify()secret {String | Buffer}
- - either the secret for HMAC algorithms, or the PEM encoded private key for RSA and ECDSA.See the jsonwebtoken package docs for other available options.
The returned promise
resolves with the payload or fails with an error.
auth.hooks.authenticate(strategies)¶
@feathersjs/authentication
only includes a single hook. This bundled
authenticate
hook is used to register an array of authentication strategies on a service method.
注解
This should usually be used on your /authentication
service. Without it,
you can hit the authentication
service and generate a JWT accessToken
without authentication (ie. anonymous authentication).
app.service('authentication').hooks({
before: {
create: [
// You can chain multiple strategies
auth.hooks.authenticate(['jwt', 'local']),
],
remove: [
auth.hooks.authenticate('jwt')
]
}
});
Authentication Events¶
The login
and logout
events are emitted on the app
object
whenever a client successfully authenticates or “logs out”. (With JWT,
logging out doesn’t invalidate the JWT. (Read the section on JWT for
details.) These events are only emitted on the server.
app.on(‘login’, callback))¶
app.on(‘logout’, callback))¶
These two events use a callback
function with the same signature.
result
{Object} - The finalcontext.result
from theauthentication
service. Unless you customize thecontext.response
in an after hook, this will only contain theaccessToken
, which is the JWT.meta
{Object} - information about the request. The ``meta`` data varies per transport / provider as follows.Using
@feathersjs/express/rest
provider
{String} - will always be"rest"
req
{Object} - the Express request object.res
{Object} - the Express response object.
Using
feathers-socketio
andfeathers-primus
:provider
{String} - the transport name:socketio
orprimus
connection
{Object} - the same asparams
in the hook contextsocket
{SocketObject} - the current user’s WebSocket object. It also contains thefeathers
attribute, which is the same asparams
in the hook context.
Express Middleware¶
There is an authenticate
middleware. It is used the exact same way
as the regular Passport express middleware:
const cookieParser = require('cookie-parser');
app.post('/protected-route', cookieParser(), auth.express.authenticate('jwt'));
app.post('/protected-route-that-redirects', cookieParser(), auth.express.authenticate('jwt', {
failureRedirect: '/login'
}));
For details, see the Express middleware recipe.
Additional middleware are included and exposed, but you typically don’t need to worry about them:
emitEvents
- emitlogin
andlogout
eventsexposeCookies
- expose cookies to Feathers so they are available to hooks and services. This is NOT used by default as its use exposes your API to CSRF vulnerabilities. Only use it if you really know what you’re doing.exposeHeaders
- expose headers to Feathers so they are available to hooks and services. This is NOT used by default as its use exposes your API to CSRF vulnerabilities. Only use it if you really know what you’re doing.failureRedirect
- support redirecting on auth failure. Only triggered ifhook.redirect
is set.successRedirect
- support redirecting on auth success. Only triggered ifhook.redirect
is set.setCookie
- support setting the JWT access token in a cookie. Only enabled if cookies are enabled. Note: Feathers will NOT read an access token from a cookie. This would expose the API to CSRF attacks. ThissetCookie
feature is available primarily for helping with Server Side Rendering.
Complete Example¶
Here’s an example of a Feathers server that uses
@feathersjs/authentication
for local authentication.
const feathers = require('@feathersjs/feathers');
const express = require('@feathersjs/express');
const socketio = require('@feathersjs/socketio');
const auth = require('@feathersjs/authentication');
const local = require('@feathersjs/authentication-local');
const jwt = require('@feathersjs/authentication-jwt');
const memory = require('feathers-memory');
const app = express(feathers());
app.configure(express.rest())
.configure(socketio())
.use(express.json())
.use(express.urlencoded({ extended: true }))
.configure(auth({ secret: 'supersecret' }))
.configure(local())
.configure(jwt())
.use('/users', memory())
.use('/', express.static(__dirname + '/public'))
.use(express.errorHandler());
app.service('users').hooks({
// Make sure `password` never gets sent to the client
after: local.hooks.protect('password')
});
app.service('authentication').hooks({
before: {
create: [
// You can chain multiple strategies
auth.hooks.authenticate(['jwt', 'local'])
],
remove: [
auth.hooks.authenticate('jwt')
]
}
});
// Add a hook to the user service that automatically replaces
// the password with a hash of the password, before saving it.
app.service('users').hooks({
before: {
find: [
auth.hooks.authenticate('jwt')
],
create: [
local.hooks.hashPassword({ passwordField: 'password' })
]
}
});
const port = 3030;
let server = app.listen(port);
server.on('listening', function() {
console.log(`Feathers application started on localhost:${port}`);
});


As Mixin is a public blockchain, whose data is fully open to the world, all developers can use the blockchain to develop anything.
Mixin Messenger is the first app developed on the Mixin blockchain. To make things easier for both developers and end users, it's recommended to use the Mixin Messenger Open API to develop your apps.
The first step to use the Mixin Messenger Open API is to create an app by visiting the Mixin Developers dashboard https://developers.mixin.one/dashboard.
Give your app a name and description, and define an OAuth callback URL, it may be a standard HTTP(S) link, or your own schema if you want to use the Mixin API in a client app.>
The Mixin Messenger uses a slightly modified OAuth 2 protocol to manage user authentication and permissions. The first step is to request an authorization code by redirecting your user to the URL below.
https://mixin.one/oauth/authorize?client_id=CLIENT_ID&scope=SCOPE&code_challenge=PKCE
CLIENT_ID is the UUID of your app in Mixin Developers dashboard, and there are three supported available scopes for now.
The code_challenge PKCE is optional, and only required if you are building a client app and don't want to expose your client secret. The only supported PKCE method is S256.
Then the user will be guided to scan the QR code on the authorization page, once they approved your request, the user will be redirected to your registered redirect URI in your Mixin Developers dashboard.
Once you have the authorization code, you are ready to request an access token.
POST https://api.mixin.one/oauth/token { "client_id": "CLIENT_ID", "code": "authorization code from step above", "client_secret": "optional client secret", "code_verifier": "optional PKCE code verifier" }
You must choose between the client_secret and code_verifier param, if you are requesting the API from your secret server, it's recommended to use client_secret. And if you are using the API in your client app, it's not safe to expose your client_secret there, you need to use the code_verifier along with code_challenge in step above.
If all correct, you will get a JSON response including the access_token and the scopes user have granted to your app. The scopes user granted may be less than what you requested.
With the access token from step above, you can access the Mixin API if you have the requested permissions.
GET -H "Authorization: Bearer ACCESS_TOKEN" https://api.mixin.one/me => { "data": { "type": "user", "user_id": "773e5e77-4107-45c2-b648-8fc722ed77f5", "name": "Team Mixin", "identity_number": "7000" } }
We have two more guides about the most important Mixin features: message and payment.
Stay tuned for our upcoming API reference for all available interfaces.


| Package | Description |
|---|---|
| org.apache.taverna.server.master |
The core of the implementation of Taverna Server, including the
implementations of the SOAP and REST interfaces.
|
| org.apache.taverna.server.master.api |
API interfaces for the main service classes.
|
| org.apache.taverna.server.master.common |
This package contains the common XML elements used throughout Taverna Server's various interfaces.
|
| org.apache.taverna.server.master.factories |
These interfaces define the principal way for the factories of
worker classes to be invoked.
|
| org.apache.taverna.server.master.identity |
Implementations of beans that map global user identities to local
usernames.
|
| org.apache.taverna.server.master.interaction |
This package contains the Atom feed implementation for interactions for a particular workflow run.
|
| org.apache.taverna.server.master.interfaces |
Interfaces to the main worker classes that provide the magical power
that drives the webapp front-end.
|
| org.apache.taverna.server.master.localworker |
Implementation of a Taverna Server back-end that works by forking off
workflow executors on the local system.
|
| org.apache.taverna.server.master.notification |
The notification fabric and implementations of notification dispatchers
that support subscription.
|
| org.apache.taverna.server.master.notification.atom |
This package contains the Atom feed implementation within Taverna Server.
|
| org.apache.taverna.server.master.rest |
This package contains the RESTful interface to Taverna Server.
|
| org.apache.taverna.server.master.rest.handler |
This package contains type handlers for the RESTful interface to Taverna Server.
|
| org.apache.taverna.server.master.soap |
This package contains the SOAP interface to Taverna Server.
|
| org.apache.taverna.server.master.utils |
Miscellaneous utility classes.
|
| org.apache.taverna.server.master.worker |
A Taverna Server back-end that works by forking off workflow executors.
|
| Class and Description |
|---|
| File
Represents a file in the working directory of a workflow instance run, or in
some sub-directory of it.
|
| Input
This represents the assignment of inputs to input ports of the workflow.
|
| Listener
An event listener that can be attached to a
TavernaRun . |
| LocalIdentityMapper
This interface describes how to map from the identity understood by the
webapp to the identity understood by the local execution system.
|
| Policy
Simple policy interface.
|
| RunStore
Interface to the mechanism that looks after the mapping of names to runs.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| TavernaSecurityContext
Security context for a workflow run.
|
| UriBuilderFactory
How to manufacture URIs to workflow runs.
|
| Class and Description |
|---|
| Listener
An event listener that can be attached to a
TavernaRun . |
| Policy
Simple policy interface.
|
| RunStore
Interface to the mechanism that looks after the mapping of names to runs.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| TavernaSecurityContext
Security context for a workflow run.
|
| UriBuilderFactory
How to manufacture URIs to workflow runs.
|
| Class and Description |
|---|
| DirectoryEntry
An entry in a
Directory representing a file or sub-directory. |
| Input
This represents the assignment of inputs to input ports of the workflow.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| Class and Description |
|---|
| Listener
An event listener that can be attached to a
TavernaRun . |
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| Class and Description |
|---|
| LocalIdentityMapper
This interface describes how to map from the identity understood by the
webapp to the identity understood by the local execution system.
|
| RunStore
Interface to the mechanism that looks after the mapping of names to runs.
|
| Class and Description |
|---|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| UriBuilderFactory
How to manufacture URIs to workflow runs.
|
| Class and Description |
|---|
| Directory
Represents a directory that is the working directory of a workflow run, or a
sub-directory of it.
|
| Directory.ZipStream
A simple pipe that produces the zipped contents of a directory.
|
| DirectoryEntry
An entry in a
Directory representing a file or sub-directory. |
| File
Represents a file in the working directory of a workflow instance run, or in
some sub-directory of it.
|
| Input
This represents the assignment of inputs to input ports of the workflow.
|
| Listener
An event listener that can be attached to a
TavernaRun . |
| Policy
Simple policy interface.
|
| SecurityContextFactory
How to create instances of a security context.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| TavernaSecurityContext
Security context for a workflow run.
|
| Class and Description |
|---|
| Listener
An event listener that can be attached to a
TavernaRun . |
| LocalIdentityMapper
This interface describes how to map from the identity understood by the
webapp to the identity understood by the local execution system.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| Class and Description |
|---|
| MessageDispatcher
The interface supported by all notification message dispatchers.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| Class and Description |
|---|
| MessageDispatcher
The interface supported by all notification message dispatchers.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| UriBuilderFactory
How to manufacture URIs to workflow runs.
|
| Class and Description |
|---|
| DirectoryEntry
An entry in a
Directory representing a file or sub-directory. |
| File
Represents a file in the working directory of a workflow instance run, or in
some sub-directory of it.
|
| Input
This represents the assignment of inputs to input ports of the workflow.
|
| Listener
An event listener that can be attached to a
TavernaRun . |
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| Class and Description |
|---|
| Directory.ZipStream
A simple pipe that produces the zipped contents of a directory.
|
| File
Represents a file in the working directory of a workflow instance run, or in
some sub-directory of it.
|
| Class and Description |
|---|
| Directory
Represents a directory that is the working directory of a workflow run, or a
sub-directory of it.
|
| File
Represents a file in the working directory of a workflow instance run, or in
some sub-directory of it.
|
| Class and Description |
|---|
| Directory
Represents a directory that is the working directory of a workflow run, or a
sub-directory of it.
|
| DirectoryEntry
An entry in a
Directory representing a file or sub-directory. |
| File
Represents a file in the working directory of a workflow instance run, or in
some sub-directory of it.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| Class and Description |
|---|
| Directory
Represents a directory that is the working directory of a workflow run, or a
sub-directory of it.
|
| Input
This represents the assignment of inputs to input ports of the workflow.
|
| Listener
An event listener that can be attached to a
TavernaRun . |
| Policy
Simple policy interface.
|
| RunStore
Interface to the mechanism that looks after the mapping of names to runs.
|
| SecurityContextFactory
How to create instances of a security context.
|
| TavernaRun
The interface to a taverna workflow run, or "run" for short.
|
| TavernaSecurityContext
Security context for a workflow run.
|
| UriBuilderFactory
How to manufacture URIs to workflow runs.
|
Copyright © 2015–2018 The Apache Software Foundation. All rights reserved.


Adult Services Reference Desk
Back to
the Map!
We can answer almost any question you have.
We also offer computer and electronic resource help.


PART 4. [OLD] PROTECTION OF PROPERTY OF
PERSONS UNDER DISABILITY AND MINORS--REPEALED
§§560:5-401 to 560:5-432 REPEALED. L 2004, c 161, §37.


|
|
{{::testString.id}} | {{::testString.blankStr}} | {{::testString.creditCardStr}} | {{::testString.emailStr}} | {{::testString.inListStr}} | {{::testString.matchesStr}} | {{::testString.maxSizeStr}} | {{::testString.minSizeStr}} | {{::testString.notEqualStr}} | {{::testString.sizeStr}} | {{::testString.textareaStr}} | {{::testString.uniqueStr}} | {{::testString.urlStr}} |


Link 1
Link 2
Link 3
Link 4
Top Block
This is an aligned top item.
This is an aligned item.
This is an aligned bottom item.


Toggle navigation
Mokonge Agro-Tech
Homepage
Farmer
Seller
Advisory
Welcome, Mokonge
Logout
Manage Your Site
Manage Account
Add User
Change Password
Adminstrator pannel
Dashboard
SMS
Received Msg
Sent Msg
Subscriber
Broadcast
User Data
Update News
Crawler
Statistics
List of Sent Messages


|
Maileon PHP client
1.3.2
Easily integrate your PHP application with Maileon.
|
Public Member Functions | |
| createContact ($contact, $syncMode, $src="", $subscriptionPage="", $doi=FALSE, $doiPlus=FALSE, $doiMailingKey="") | |
| createContactByExternalId ($contact, $syncMode, $src="", $subscriptionPage="", $doi=FALSE, $doiPlus=FALSE, $doiMailingKey="") | |
| getContact ($contactId, $checksum, $standard_fields=array(), $custom_fields=array(), $ignoreChecksum=false) | |
| getContactsCount () | |
| getContacts ($page_index=1, $page_size=100, $standard_fields=array(), $custom_fields=array()) | |
| getContactByEmail ($email, $standard_fields=array(), $custom_fields=array()) | |
| getContactsByEmail ($email, $standard_fields=array(), $custom_fields=array()) | |
| getContactsByExternalId ($externalId, $standard_fields=array(), $custom_fields=array()) | |
| getContactsByFilterId ($filterId, $page_index=1, $page_size=100, $standard_fields=array(), $custom_fields=array()) | |
| getCountContactsByFilterId ($filterId) | |
| getCountActiveContactsByFilterId ($filterId) | |
| updateContact ($contact, $checksum="", $src=null, $subscriptionPage=null, $triggerDoi=FALSE, $doiMailingKey=null, $ignoreChecksum=false) | |
| synchronizeContacts ($contacts, $permission=null, $syncMode=null, $useExternalId=false, $ignoreInvalidContacts=false, $reimportUnsubscribedContacts=true, $overridePermission=true, $updateOnly=false, $preferMaileonId=false) | |
| unsubscribeContactByEmail ($email, $mailingId="", $reasons=null) | |
| addUnsubscriptionReasonsToUnsubscribedContact ($id, $checksum=null, $reasons=null, $ignore_checksum=false) | |
| unsubscribeContactById ($id, $mailingId="", $reasons=null) | |
| unsubscribeContactByExternalId ($externalId, $mailingId="", $reasons=null) | |
| unsubscribeContactByExternalIdFromMultipleAccounts ($externalId, $nlAccountIds=array()) | |
| getBlockedContacts ($standardFields=array(), $customFields=array(), $pageIndex=1, $pageSize=1000) | |
| deleteContact ($id) | |
| deleteContactByEmail ($email) | |
| deleteContactsByExternalId ($externalId) | |
| deleteAllContacts ($authorized="no") | |
| createCustomField ($name, $type= 'string') | |
| getCustomFields () | |
| renameCustomField ($oldName, $newName) | |
| deleteCustomField ($name) | |
| deleteStandardFieldValues ($name) | |
| deleteCustomFieldValues ($name) | |
| Public Member Functions inherited from com_maileon_api_AbstractMaileonService | |
| __construct (array $config) | |
| setDebug ($isDebug) | |
| isDebug () | |
| get ($resourcePath, $queryParameters=array(), $mimeType= 'application/vnd.maileon.api+xml', $deserializationType=null) | |
| put ($resourcePath, $payload="", $queryParameters=array(), $mimeType= 'application/vnd.maileon.api+xml', $deserializationType=null) | |
| post ($resourcePath, $payload="", $queryParameters=array(), $mimeType= 'application/vnd.maileon.api+xml', $deserializationType=null, $contentType=null, $contentLength=null) | |
| delete ($resourcePath, $queryParameters=array(), $mimeType= 'application/vnd.maileon.api+xml', $deserializationType=null) | |
Additional Inherited Members | |
| Static Public Attributes inherited from com_maileon_api_AbstractMaileonService | |
| static | $MAILEON_XML_MIME_TYPE = 'application/vnd.maileon.api+xml' |
| Protected Member Functions inherited from com_maileon_api_AbstractMaileonService | |
| appendArrayFields ($params, $name, $fieldValues) | |
| Protected Attributes inherited from com_maileon_api_AbstractMaileonService | |
| $configuration | |
| $encodedApiKey | |
| $debug = false | |
| $throwException = true | |
| $proxy_host | |
| $proxy_port = 80 | |
| $timeout | |
This service wrapps the REST API calls for the contact features.
Definition at line 9 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::createContact | ( | $contact, | |
| $syncMode, | |||
$src = "" , |
|||
$subscriptionPage = "" , |
|||
$doi = FALSE , |
|||
$doiPlus = FALSE , |
|||
$doiMailingKey = "" |
|||
| ) |
Creates or updates a contact and optionally triggers a double opt-in (doi) process. Note that none of the attributes is required.
| com_maileon_api_contacts_Contact | $contact | the contact to create or update; if no permission is set, the Maileon default permission "NONE" will be used |
| com_maileon_api_contacts_SynchronizationMode | $syncMode | the synchronization mode to employ |
| string | $src | A string intended to describe the source of the contact. If provided, the string will be stored with the doi process. |
| string | $subscriptionPage | In case where this method was called by a subscription page, this string offers the possibility to keep track of it for use in reports. |
| bool | $doi | Tells whether a double opt-in process should be started for the created contact. Note that the status code returned for this request does not mean that the doi process succeeded. |
| bool | $doiPlus | This parameter is ignored if doi is not provided or false. In case the doi process succeeds, Maileon will be allowed to track opens and clicks of the contact. |
| string | $doiMailingKey | This parameter is ignored if doi is not provided or false. References the doi mailing to be used. If not provided, the default doi mailing will be used. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 41 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::createContactByExternalId | ( | $contact, | |
| $syncMode, | |||
$src = "" , |
|||
$subscriptionPage = "" , |
|||
$doi = FALSE , |
|||
$doiPlus = FALSE , |
|||
$doiMailingKey = "" |
|||
| ) |
Creates or updates a contact based on the external ID and optionally triggers a double opt-in (doi) process. Note that none of the attributes is required. Also note: this call returns 409 Conflict if more then one contact with the given external ID exists as it is impossible to determine the correct contact to update.
| com_maileon_api_contacts_Contact | $contact | the contact to create or update |
| com_maileon_api_contacts_SynchronizationMode | $syncMode | the synchronization mode to employ |
| string | $src | A string intended to describe the source of the contact. If provided, the string will be stored with the doi process. |
| string | $subscriptionPage | In case where this method was called by a subscription page, this string offers the possibility to keep track of it for use in reports. |
| bool | $doi | Tells whether a double opt-in process should be started for the created contact. Note that the status code returned for this request does not mean that the doi process succeeded. |
| bool | $doiPlus | This parameter is ignored if doi is not provided or false. In case the doi process succeeds, Maileon will be allowed to track opens and clicks of the contact. |
| string | $doiMailingKey | This parameter is ignored if doi is not provided or false. References the doi mailing to be used. If not provided, the default doi mailing will be used. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 97 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContact | ( | $contactId, | |
| $checksum, | |||
$standard_fields = array() , |
|||
$custom_fields = array() , |
|||
$ignoreChecksum = false |
|||
| ) |
Return a contact using the maileon contact id. This resource is intended to be used in profile update pages to prefill profile update forms. In order to prevent form fields manipulation, a checksum of the maileon contact id is required as parameter. Please refer to the documentation of the profile update pages for more details about how to get the maileon contact id and the corresponding checksum.
| string | $contactId | the maileon contact id |
| string | $checksum | the checksum of the maileon contact id |
| string[] | $standard_fields the standard fields to retrieve with the contact | |
| string[] | $custom_fields the custom fields to retrieve with the contact | |
| bool | $ignoreChecksum | if set to true, no checksum is required |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 139 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContactsCount | ( | ) |
This method returns the number of contacts in the maileon newsletter account.
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 162 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContacts | ( | $page_index = 1 , |
|
$page_size = 100 , |
|||
$standard_fields = array() , |
|||
$custom_fields = array() |
|||
| ) |
Returns a page of contacts in the account.
| number | $page_index | the index of the result page to fetch |
| number | $page_size | the number of results to fetch per page |
| string[] | $standard_fields the standard fields to retrieve for the contacts | |
| string[] | $custom_fields the custom fields to retrieve for the contacts |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 184 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContactByEmail | ( | $email, | |
$standard_fields = array() , |
|||
$custom_fields = array() |
|||
| ) |
Returns a contact with the provided email address.
| string | the email address to retrieve a contact for | |
| string[] | $standard_fields the standard fields to return with the contact | |
| string[] | $custom_fields the custom fields to return with the contact |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 212 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContactsByEmail | ( | $email, | |
$standard_fields = array() , |
|||
$custom_fields = array() |
|||
| ) |
Returns a list of contacts with the provided email address.
| string | the email address to retrieve a contact for | |
| string[] | $standard_fields the standard fields to return with the contact | |
| string[] | $custom_fields the custom fields to return with the contact |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 238 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContactsByExternalId | ( | $externalId, | |
$standard_fields = array() , |
|||
$custom_fields = array() |
|||
| ) |
Retrieves all contacts with a given external ID.
| string | $externalId | the external ID to search for |
| string[] | $standard_fields | |
| string[] | $custom_fields |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 261 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getContactsByFilterId | ( | $filterId, | |
$page_index = 1 , |
|||
$page_size = 100 , |
|||
$standard_fields = array() , |
|||
$custom_fields = array() |
|||
| ) |
Retrieves all contacts with a given contact filter ID.
| string | $filterId | the filter ID to use to select contacts |
| string[] | $standard_fields | |
| string[] | $custom_fields |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 284 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getCountContactsByFilterId | ( | $filterId | ) |
Retrieves the number of contacts matching a given contact filter ID.
| string | $filterId | the filter ID to use to select contacts |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 305 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getCountActiveContactsByFilterId | ( | $filterId | ) |
Retrieves the number of active contacts matching a given contact filter ID.
| string | $filterId | the filter ID to use to select contacts |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 320 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::updateContact | ( | $contact, | |
$checksum = "" , |
|||
$src = null , |
|||
$subscriptionPage = null , |
|||
$triggerDoi = FALSE , |
|||
$doiMailingKey = null , |
|||
$ignoreChecksum = false |
|||
| ) |
This methods updates the data of a Maileon contact identifying a contact by its internal Maileon ID
| com_maileon_api_contacts_Contact | $contact | The contact object to send to Maileon. |
| string | $checksum | This is the checksum that must be used when the request comes from a user, see documentation under http://dev.maileon.com for details. |
| string | $src | The source that shall be passed to the API. |
| string | $subscriptionPage | The subscription page the request comes from. |
| boolean | $triggerDoi | If true, a DOI mailing will be triggered. |
| string | $doiMailingKey | If this parameter is set, the DOI mailing with the given ID will be triggered. If not set, the default DOI Mailing will be triggered. |
| string | $ignoreChecksum | If this is true, the checksum will not be validated. This is only valid if the request is NOT triggered by the contact (e.g. on a profile change landing page) but from a third party system. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 347 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::synchronizeContacts | ( | $contacts, | |
$permission = null , |
|||
$syncMode = null , |
|||
$useExternalId = false , |
|||
$ignoreInvalidContacts = false , |
|||
$reimportUnsubscribedContacts = true , |
|||
$overridePermission = true , |
|||
$updateOnly = false , |
|||
$preferMaileonId = false |
|||
| ) |
Synchronizes a list of contacts with the contacts in the account and returns a detailed report with stats and validation errors.
| com_maileon_api_contacts_Contacts | $contacts | the contacts to synchronize |
| com_maileon_api_contacts_Permission | $permission | the permission to set for the contacts |
| com_maileon_api_contacts_SynchronizationMode | $syncMode | the sync mode to use |
| string | $useExternalId | if set to true, the external id is used as identifier for the contacts. Otherwise the email address is used as identifier. |
| string | $ignoreInvalidContacts | if set to true, invalid contacts are ignored and the synchronization succeeds for valid contacts. |
| string | $reimportUnsubscribedContacts | if set to true, unsubscribed contacts will be imported, if false, they will be ommitted |
| boolean | $overridePermission | if set to true the permission of existing and non existing contacts will be overwridden, if false, the permission will be used for new contacts only and existing contacts will not be influenced. |
| boolean | $updateOnly | If true, only existing contacts are updated and no new contacts are created |
| boolean | $preferMaileonId | If true, Maileon tries identifying contacts by Maileon-ID, if available. Fallback is always the email address. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 398 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::unsubscribeContactByEmail | ( | $email, | |
$mailingId = "" , |
|||
$reasons = null |
|||
| ) |
This method unsubscribes a contact from Maileon using the contact's email adress.
| string | The email address of the contact. | |
| long | $mailingId | The ID of the mailing to assign the unsubscribe to. the mailing must have been sent, i.e. be sealed. |
| array | $reasons | an array of reasons or a single reason (string). Unsubscription reasons have two layers of information, see http://dev.maileon.com/api/rest-api-1-0/contacts/unsubscribe-contacts-by-email for more details about the format. The parameter(s) will be url-encoded by the client, you do not need to provide urlencoded strings. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 433 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::addUnsubscriptionReasonsToUnsubscribedContact | ( | $id, | |
$checksum = null , |
|||
$reasons = null , |
|||
$ignore_checksum = false |
|||
| ) |
This method adds unsubscription reasons to an unsubscribed contact. The contact must already be unsubscribed, otherwise 400 will be returned by the PAI
| int | $id | The ID of the contact. |
| string | $checksum | The checksum generated by Maileon |
| array | $reasons | an array of reasons or a single reason (string). Unsubscription reasons have two layers of information, see http://dev.maileon.com/api/rest-api-1-0/contacts/unsubscribe-contacts-by-email for more details about the format. The parameter(s) will be url-encoded by the client, you do not need to provide urlencoded strings. |
| boolean | $ignore_checksum | If the call comes from an authorized system instead of the user you might ignore the checksum |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 467 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::unsubscribeContactById | ( | $id, | |
$mailingId = "" , |
|||
$reasons = null |
|||
| ) |
This method unsubscribes a contact from Maileon using the Maileon id.
| int | $id | |
| long | $mailingId | The ID of the mailing to assign the unsubscribe to. the mailing must have been sent, i.e. be sealed. |
| array | $reasons | an array of reasons or a single reason (string). Unsubscription reasons have two layers of information, see http://dev.maileon.com/api/rest-api-1-0/contacts/unsubscribe-contacts-by-maileon-id for more details about the format. The parameter(s) will be url-encoded by the client, you do not need to provide urlencoded strings. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 500 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::unsubscribeContactByExternalId | ( | $externalId, | |
$mailingId = "" , |
|||
$reasons = null |
|||
| ) |
This method unsubscribes a contact from Maileon using the external id.
| string | $externalId | The external ID of the contact. |
| long | $mailingId | The ID of the mailing to assign the unsubscribe to. the mailing must have been sent, i.e. be sealed. |
| array | $reasons | an array of reasons or a single reason (string). Unsubscription reasons have two layers of information, see http://dev.maileon.com/api/rest-api-1-0/contacts/unsubscribe-contacts-external-id for more details about the format. The parameter(s) will be url-encoded by the client, you do not need to provide urlencoded strings. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 533 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::unsubscribeContactByExternalIdFromMultipleAccounts | ( | $externalId, | |
$nlAccountIds = array() |
|||
| ) |
This method unsubscribes a contact from Maileon from several accounts (owner of API key must also be the same customer owning the other accounts).
| int | $externalId | |
| long | $nlaccountid | The ID of the mailing to assign the unsubscribe to. the mailing must have been sent, i.e. be sealed. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 562 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getBlockedContacts | ( | $standardFields = array() , |
|
$customFields = array() , |
|||
$pageIndex = 1 , |
|||
$pageSize = 1000 |
|||
| ) |
Returns a page of blocked contacts. Blocked contacts are contacts with available permission but that are blocked for sendouts because of blacklist matches or similar reasons such as bounce policy.
| string[] | $standardFields the standard fields to select | |
| string[] | $customFields the custom fields to select | |
| number | $pageIndex | the paging index of the page to retrieve |
| number | $pageSize | the number of results per page |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurredntacts_Contacts available at com_maileon_api_MaileonAPIResult::getResult() |
Definition at line 592 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteContact | ( | $id | ) |
This method removes a contact completely from Maileon using the maileon ID. WARNING: the contact is COMPLETELY removed, not only unsubscribed. This means that not only the contact data is removed but also all statistics change. For most usecases the unsubscribe method is more appropriate.
| string | The email address of the contact to delete. Does not need to be unique. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 616 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteContactByEmail | ( | ) |
This method removes all contacts completely from Maileon using the email address. WARNING: the contacts are COMPLETELY removed, not only unsubscribed. This means that not only the contact data is removed but also all statistics change. For most usecases the unsubscribe method is more appropriate.
| string | The email address of the contact to delete. Does not need to be unique. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 633 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteContactsByExternalId | ( | $externalId | ) |
This method removes the contacts completely from Maileon using the external id. WARNING: the contacts are COMPLETELY removed, not only unsubscribed. This means that not only the contact data is removed but also all statistics change. For most usecases the unsubscribe method is more appropriate.
| string | $external | ID The external ID of the contact to delete. Does not need to be unique. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 649 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteAllContacts | ( | $authorized = "no" | ) |
This method DELETES ALL CONTACTS. Never ever call this unless you'd prefer a career change anyway.
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 663 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::createCustomField | ( | $name, | |
$type = 'string' |
|||
| ) |
Creates a custom contact field with the provided name and data type.
| string | $name | the name of the new field |
| string | $type | the type of the new field. Valid values are 'string', 'integer', 'float', 'date' or 'boolean'. |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 684 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::getCustomFields | ( | ) |
Returns the custom contact fields defined in the account.
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 700 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::renameCustomField | ( | $oldName, | |
| $newName | |||
| ) |
Renames a custom contact field. The data type and the recorded values for the contacts remain unchanged.
| string | $oldName | the current name of the field |
| string | $newName | the new name of the field |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 718 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteCustomField | ( | $name | ) |
Deletes the custom contact field with the provided name. Note that all the values of the field get auotmatically deleted by this call.
| string | $name | the name of the field to delete |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 736 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteStandardFieldValues | ( | $name | ) |
Deletes the values of the given standard contact field for all contacts.
| string | $name | the name of the field whose values to delete |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 752 of file ContactsService.php.
| com_maileon_api_contacts_ContactsService::deleteCustomFieldValues | ( | $name | ) |
Deletes the values of the given custom contact field for all contacts.
| string | $name | the name of the field whose values to delete |
| com_maileon_api_MaileonAPIException | if there was a connection problem or a server error occurred |
Definition at line 768 of file ContactsService.php.


Welcome to Blue Gold! Please enter Your User ID and Password to Sign In
{% csrf_token %}
Forgot Password


Who Needs Financial Stability, Anyway? http://www.dirtandseeds.com/who-needs-financial-stability-anyway/
8/8/2013, 10:58:13 AM
Favs: 0
Retweets: 0
link--- layout: tweet ---
Who Needs Financial Stability, Anyway? http://www.dirtandseeds.com/who-needs-financial-stability-anyway/
8/8/2013, 10:58:13 AM
Favs: 0
Retweets: 0
link


Sleep deprivation can render your body more susceptible to disease by weakening your immune system.
The study consisted of a sleep deprived group and a regular sleep group. Both sustained their sleeping schedules for 10 days and were immunized after the 4th night.
On the 10th day, both groups were tested for their antibody response. The group getting 4 hours of sleep a night (constitutes sleep deprivation) exhibited an immune response less than 50% of a normal antibody response. This indicates that sleep deprivation weakens your immune system making you more susceptible to disease.
Images Courtesy of Professor Walker's Lecture 11 slides
Another study showed that continued sleep deprivation led to a 70% reduction in natural killer cells. A high natural killer cell count are vital in helping fight cancer. The results were so conclusive that the World Health Organization were compelled to declare "shift work" as a possible carcinogen.
Study citation: http://goo.gl/C7Pjlj


Search parameters:
- Slackware version :: slackware-13.1
- Categories :: ANY
- Search for :: packages
- Results found :: 2
- Search took :: 0 sec
Search results:
2010-04-20 14:23:00 :: package created
PACKAGE SIZE (compressed): 136 K PACKAGE SIZE (uncompressed): 370 K PACKAGE DESCRIPTION: sudo: sudo (give limited root privileges to certain users) sudo: sudo: "sudo" is a command that allows users to execute some commands as sudo: root. The /etc/sudoers file (edited with "visudo") specifies which sudo: users have access to sudo and which commands they can run. "sudo" sudo: logs all its activities to /var/log/ so the system administrator sudo: can keep an eye on things. sudo:
patches/packages/sudo-1.7.4p4-i486-3_slack13.1.txz :: package name and location
2010-09-15 18:34:00 :: package created
PACKAGE SIZE (compressed): 160 K PACKAGE SIZE (uncompressed): 420 K PACKAGE DESCRIPTION: sudo: sudo (give limited root privileges to certain users) sudo: sudo: "sudo" is a command that allows users to execute some commands as sudo: root. The /etc/sudoers file (edited with "visudo") specifies which sudo: users have access to sudo and which commands they can run. "sudo" sudo: logs all its activities to /var/log/ so the system administrator sudo: can keep an eye on things. sudo: