Get help now!
Search our florida loan forgiveness teacher,
About Us - Loan Lawyers, LLC
Loan Lawyers, LLC was founded by Matis H. Abarbanel, Esquire; and Matthew D . Bavaro, Esquire. Both Florida foreclosure lawyers are Orthodox Jews and .
http://www.fightingfloridaforeclosure.com/about-our-foreclosure-attorneys-lawyers.html
More Resources
florida loan forgiveness public service
Scott Goldstein | LinkedIn
Attorney at Loan Lawyers, LLC; Law Clerk at Consumer Law Clinic; Certified Legal . Florida Coastal School of Law; Richard Stockton College of New Jersey .
http://www.linkedin.com/pub/scott-goldstein/8/940/ba6
The following are general eligibility requirements for all borrowers seeking teacher loan forgiveness:
Fight Foreclosure Matis H. Abravanel and Matthew D. Bavaro ...
Florida foreclosure defense attorneys / lawyers in Broward County, Miami-Dade County, and Palm Beach counties in Florida. At Loan Lawyers, LLC our .
http://www.facebook.com/pages/Fight-Foreclosure-Matis-H-Abravanel-and-Matthew-D-Bavaro/154853701220158
Matthew Bavaro | LinkedIn
Matthew David Bavaro is a partner in Loan Lawyers, LLC, a South Florida law firm focusing on representing homeowners for a variety of consumer protection .
http://www.linkedin.com/in/matthewbavaro
Contact Us - Loan Lawyers, LLC
When you need Florida help, a Florida Bankruptcy lawyer may prove to be your best asset. Call 1-888-FIGHT-13 today.
http://www.fightingfloridaforeclosure.com/contact-florida-foreclosure-attorneys-lawyers.html
Matis H. Abravanel & Matthew D. Bavaro - Loan Lawyers, LLC
Florida Foreclosure, Consumer Protection and Loan Modification Attorneys. Matis H. Abravanel & Matthew D. Bavaro - Loan Lawyers, LLC main office at 377 .
http://www.hg.org/attorney/matis-h-abravanel-and-matthew-d-bavaro-loan-lawyers-llc/86468
Matthew Bavaro - About - Google+
Loan Lawyers, LLC was founded by Matis H. Abravanel, Esquire; and Matthew D. Bavaro, Esquire. Both Florida foreclosure lawyers are Orthodox Jews and .
https://plus.google.com/104942749343616836122/about
Lawyer Matthew Bavaro - Plantation Attorney - Avvo.com
Lawyers: Endorse this lawyer . I have been a resident of South Florida my entire life. . Partner at Loan Lawyers, LLC / Bavaro Legal, PA, 2003present .
http://www.avvo.com/attorneys/33317-florida-matthew-bavaro-1250203.html
Fight13.com - Plantation, Florida - Property Law, Real Estate Lawyer ...
The foreclosure lawyers at Loan Lawyers, LLC in South Florida filed a lawsuit against Bank of America for unlawful debt collection practices. They called our.
https://www.facebook.com/Fight13LoanLawyers
Loan Lawyers, Llc. in Plantation, FL - Reviews, Photos, and Directions
Loan Lawyers, Llc. in Plantation, FL. Come to Citysearch® to get information, directions, and reviews on Loan Lawyers, Llc. and other Attorneys & Legal .
http://fortlauderdale.citysearch.com/profile/660225490/plantation_fl/loan_lawyers_llc_.html
Florida Foreclosure Defense Lawyers - Loan Lawyers, LLC ...
If you have been served with a foreclosure action in Florida it is highly advisable to call a Florida foreclosure attorney immediately. At Loan Lawyers, LLC we will .
http://www.fightingfloridaforeclosure.com/florida-foreclosure-defense-attorneys-lawyers.html
Loan Lawyers, LLC
Foreclosure lawyers attorneys in Broward, Miami Dade and Palm Beach, Fort Lauderdale, Miami, Delray Beach, handle foreclosure defense, loan modification, .
http://www.fightingfloridaforeclosure.com/
Bavaro Legal PA: South Florida Personal Injury Attorneys
If you are a struggling homeowner, please click here for Loan Lawyers, LLC. . Palm Beach County (Delray Beach), and Miami-Dade County, Florida ready to .
http://www.pitrialgroup.com/
DURAN v. WELLS FARGO BANK, N.A. - July 23, 2012. - Leagle
Jul 23, 2012 . Yechezkel Rodal, Loan Lawyers, LLC, Plantation, FL, for Plaintiff. . N.A., for violations of the Florida Consumer Collection Practices Act, Fla.
http://www.leagle.com/xmlResult.aspx?xmldoc=In%20FDCO%2020120724823.xml&docbase=CsLwAr3-2007-Curr
Loan Lawyers, Llc. in Plantation, FL - YellowBot
Loan Lawyers, Llc. at 377 N State Road 7 Ste 202, Plantation, FL 33317. . Fair Debt Collection Practices Act, Florida Consumer Collection Practices Act in .
http://www.yellowbot.com/loan-lawyers-llc-plantation-fl-1.html
debt consolidation loan companies - The Sun By The Sea
lumpkin county georgia debt consolidation loan corporate bankruptcy and . bankruptcy llc insider compensation priority . chapter 7 bankruptcy attorney florida .
http://www.sunbythesea.com/while_you_were_away_past.html
Florida bankruptcy lawyer
If you are struggling with one or more of the reasons listed above, call Loan Lawyers today for a free bankruptcy consultation with one of our South Florida .
http://www.florida-bankruptcy-lawyers.com/
Miami Foreclosure Defense Lawyer | Florida Foreclosure Defense ...
If you are facing foreclosure in Miami or anywhere else in Southwest Florida, contact an experienced foreclosure defense lawyer at Shuster & Saben, LLC for help. . the Florida Bar
loan modification companies and out of state lawyers can't .
http://www.attorneyforeclosuredefense.com/
Matthew Bavaro - Google+
Matthew Bavaro - Loan Lawyers - Aventura, FL - Loan Lawyers, LLC was founded by Matis H. Abravanel, Esquire; and Matthew D. Bavaro, Esquire. Both Florida .
https://plus.google.com/104942749343616836122
WSVN-TV - Bank pays woman in foreclosed home
Oct 19, 2012 . She then called Loan Lawyers LLC to save her North Lauderdale home. Bank of America was then ordered to pay Marc more than $10,000, .
http://www.wsvn.com/news/articles/local/21008829667145/
Get A Fresh Financial Start - Thinking About Filing Bankruptcy?
Promoting the texas dwi refusal enjoyment and south carolina cash loan stewardship of dui conviction in illinois the . florida bankruptcy legal center . bankruptcy lawyers in southern new jersey . driveline systems llc and possible bankruptcy .
http://www.amosbutleraudubon.org/lost-password/
Law Week - Broward County Lawyers | Broward County Bar ...
Trial Lawyers Building 633 Southeast 3rd Avenue, Suite 4F Fort Lauderdale, FL 33301 . Florida Legal Services 508 Lucerne . Loan Lawyers, LLC 377 N. State .
http://www.browardbar.org/committee-law_week.htm
Lillian Betancourt Desmond - YouTube
The foreclosure lawyers at Loan Lawyers, LLC in South Florida filed a lawsuit against Bank of America for unlawful debt collection practices. They.
http://www.youtube.com/user/MsSmurf2012
Mager Lawyers, LLC
Mager Lawyers . Mager Lawyers, LLC. solid foundation is deeply rooted in the number and quality of significant . Florida & Washington, District of Columbia .
http://www.magerlawyers.com/
Florida Loan Modification|Attorney|West Palm Beach|Mortgage ...
. in a Florida Loan Modification or West Palm Beach Loan Modification Attorney . Legal Assistance Center, L.L.C. law firm is committed to assisting clients who .
http://www.thelegalassistancecenter.com/mortgageassistance.html
North Miami Real Estate Attorney | Florida Foreclosure Lawyer | Ft ...
Law Offices of Jake Miller, LLC - Miami Real Estate Attorney. Serving Clients Throughout South Florida Loan Modifications -- Deed Transfers Short Sales -- .
http://www.am-pa.com/
100% Guaranteed - 100% Guaranteed - HNHfoundation
Weight of cash quick loans the dwi trial NATION. WON Screening Calendar . bankruptcy attorneys in houston tx . bankruptcy trustees for orlando florida. buying a homes after . driveline systems llc and possible bankruptcy bankruptcy car .
http://www.hnhfoundation.org/conatct-us.html
Find Loan Modification Miami, Florida Law Firms - Lawyers.com
Find listings and reviews for Loan Modification law firms in Miami, Florida on Lawyers.com. . Follow Lawyers.com on Facebook Follow Lawyers.com on Twitter Follow Lawyers.com . Amerihope Alliance Legal Services, LLC (Miami, Florida) .
http://www.lawyers.com/loan-modification/miami/florida/law-firms
The Student Loan Lawyer - CT Attorney Joshua Cohen For all of ...
For all of your student loan issues. . If you are an attorney looking for more information on the upcoming Student Loan Law Workshop, please visit the Workshop .
http://thestudentloanlawyer.com/
Payday Cash Loan, 2 Minute App - National Cash Advance
payday loans checking account not required . florida regulation of payday loan . loans throughout the home equity loan no cash state and bankruptcy lawyer . Properties LLC; Town and how to repair a credit score Village Transportation .
http://www.investinvermont.org/borrowers2
Florida Mortgage Fraud - The Law - Florida Attorney General
address: Attorney General of Florida The Capitol . This includes foreclosure rescue services or loan modification services related to foreclosures. The act also .
http://www.myfloridalegal.com/mfraud.nsf/pages/law


@main("API Documentation", 2) {
Task data is represented in a flat JSON structure, like so:
{ "id": 1234, "completed": false, "description": "Task to be done", "created":<PHONE_NUMBER>950, "priority": 0 }
Integer [Nullable]
The ID is the unique numerical ID associated with a specific task. The ID will be automatically
generated when the task is created. A task will never be served with a null
id
value.
Boolean
Whether or not a task has been marked completed by the user.
String [MaxLength=254]
The task that must be accomplished before the user should mark it as complete.
Integer
The unix timestamp (in milliseconds) of when this task was created. Any provided value is ignored when creating or updating a task.
Integer
(Unused) This field is reserved for future use to indicate the relative priority with which the user intends to accomplish this task.
GET @controllers.api.routes.TaskApi.schema()Returns
<Task JSON>
Returns a blank task with fields set to their default values.
POST @controllers.api.routes.TaskApi.create() { "completed": true, "description": "Finish API documentation", "created": 0, "priority": 0 }Returns
<Task JSON>
This request must be made as type application/json
.
Creates a new task. Will return a 201 CREATED
response with the Location
header
set to the url needed to GET the new task. The body will contain the Task JSON, updated
with the correct id and created values.
GET @controllers.api.routes.TaskApi.getList(1, 20)Returns
{ "items": [ <Task JSON>, <Task JSON>, [...] <Task JSON>, <Task JSON> ], "total": 1234, "size": 20, "page": 1 }
Returns a paginated list of all user tasks. Size of the return list is controlled by the
size
parameter, constrained to a minimum of 1 and a maximum of 50 with a default of 10. The offset of the returned
list is controlled by the page
parameter, constrained to a minimum of 0, and a maximum of
the total number of items divided by size, with a default of 0.
If the supplied values fall outside those ranges, the returned values will indicate the values used.
GET @controllers.api.routes.TaskApi.get(42)Returns
<Task JSON>
Returns the Task with the id specified in the url. Will return 404 Not Found
if there is no task with a matching id.
POST @controllers.api.routes.TaskApi.get(42) { "id": 42, "completed": true, "description": "Finish API documentation", "created":<PHONE_NUMBER>950, "priority": 0 }Returns
<Task JSON>
This request must be made as type application/json
.
Updates and returns the task with the id specified in the url.
Any altered values in the id
or created
fields will be ignored.
DELETE @controllers.api.routes.TaskApi.delete(42)Returns
N/A
Deletes the task with the id specified in the url. Returns 204 NO CONTENT
.


Open a dataset with a permanent dataset name and assign that name for the session and/or create a permanent dataset name for a SAV or ZSAV file
STATS GETSET DATASET
FILE = file specification
CONFLICT = NONAME** or OVERRIDE
ASSIGNCUSTOMDSN = YES or NO**
CUSTOMDSN = dataset name
ASSIGNSESSIONDSN = YES or NO**
/HELP
* Required
** Default
/HELP displays this help and does nothing else.
STATS GETSET DATASET
FILE = "c:/data/mydata.sav"
CONFLICT = OVERRIDE.
STATS GETSET DATASET
ASSIGNCUSTOMDSN = YES CUSTOMDSN = mydata.
Any data file opened or created in SPSS Statistics is a dataset. It may or may not have a dataset name. A name allows it to be referred to in syntax in order to make it the active dataset or to perform other operations involving datasets. A dataset that does not have a name will be closed if a different dataset is made active.
A dataset name is automatically assigned when data are opened via the user interface. However, the name may be different each time the data file is opened. (Names are not automatically assigned when the data are read using syntax.)
This command provides a way to assign a permanent dataset name to an SPSS data file (.SAV or .ZSAV). That name can be applied if the data file is opened using this command.The command provides two possible actions:
FILE specifies the name of an SAV or ZSAV data file to be opened. If the file contains a permanent dataset name, that name is assigned to the opened dataset.
CONFLICT specifies what to do if the dataset name is already in use. By default, no dataset name is assigned. Specifying OVERRIDE causes the name to be transferred to the newly opened dataset. Since the name is removed from the previous holder and the newly opened one becomes active, the other dataset is closed without saving any changes. Taking the name of the active dataset is not considered a conflict.
The remaining keywords are used to create a permanent dataset name.
ASSIGNCUSTOMDSN and ASSIGNSESSIONDSN specify that a custom dataset name or the current dataset name of the active dataset should be set as the permanent dataset name. It will be saved when the dataset is saved as an SAV or ZSAV file.
The custom name to be assigned is specified with CUSTOMDSN.
© Copyright IBM Corp. 1989, 2015


A News & Sentiment Analytics Search Engine
Do you want to save changes you made to document before closing?
If you don't save, your changes will be lost.


CHARLES • YEAR NINE
LEARNING
TEACHING STUDENTS TO THINK
Academic excellence is achieved when students and teachers share a love of learning. Extending beyond the curriculum, we explore each subject in richness and depth. The same dedication is also brought to music, sports and the arts. A Winchester education is self-motivated, rounded and encourages a culture of curiosity and exploration.
Learn More
LIVING
A HAPPY BALANCE
Pastoral care is never behind the scenes at Winchester. The school operates as a fully-integrated community, where Housemasters, house teams, senior staff and teachers (known as dons) are all on-hand to support the boys throughout their school day, and their school career. Providing a sense of community and an appreciation of individual perspectives is not only our aim, but also our proudest achievement.
FIND OUT MORE
ADMISSIONS
SUPPORTING YOUR APPLICATION
We have our own unique admissions process. We look for boys with enquiring minds and natural intelligence. Our founder’s ethos was to educate such boys, whatever their background, hence our generous bursary provision. Experienced staff assist in every stage of the process, from initial inquiry through to choosing a house, to sitting the entrance exams.
REVEAL MORE
BOOK AN OPEN DAY


Copyright © 2015 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.
The bulk of the text of this specification is also available in the WHATWG Web Applications 1.0 specification, under a license that permits reuse of the specification text.
This specification defines two mechanisms for communicating between browsing contexts in HTML documents.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the most recently formally published revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
If you wish to make comments regarding this document, you can enter feedback using this form:
You can also e-mail feedback to<EMAIL_ADDRESS>(subscribe, archives), or<EMAIL_ADDRESS>(subscribe, archives). All feedback is welcome.
Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should join the aforementioned mailing lists and take part in the discussions.
The latest stable version of the editor's draft of this specification is always available on the W3C CVS server and in the WHATWG Subversion repository. The latest editor's working copy (which may contain unfinished text in the process of being prepared) contains the latest draft text of this specification (amongst others). For more details, please see the WHATWG FAQ.
Notifications of changes to this specification are sent along with notifications of changes to related specifications using the following mechanisms:
svn checkout http://svn.whatwg.org/webapps/
The W3C Web Applications Working Group is the W3C working group responsible for this specification's progress along the W3C Recommendation track. This specification is the 10 March 2015 Editor's Draft.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
MessageEvent
interfacesAll diagrams, examples, and notes in this specification are non-normative, as are all sections explicitly marked non-normative. Everything else in this specification is normative.
The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119]
Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or "return false and abort these steps") are to be interpreted with the meaning of the key word ("must", "should", "may", etc) used in introducing the algorithm.
Some conformance requirements are phrased as requirements on attributes, methods or objects. Such requirements are to be interpreted as requirements on user agents.
Conformance requirements phrased as algorithms or specific steps may be implemented in any manner, so long as the end result is equivalent. (In particular, the algorithms defined in this specification are intended to be easy to follow, and not intended to be performant.)
The only conformance class defined by this specification is user agents.
User agents may impose implementation-specific limits on otherwise unconstrained inputs, e.g. to prevent denial of service attacks, to guard against running out of memory, or to work around platform-specific limitations.
When support for a feature is disabled (e.g. as an emergency measure to mitigate a security problem, or to aid in development, or for performance reasons), user agents must act as if they had no support for the feature whatsoever, and as if the feature was not mentioned in this specification. For example, if a particular feature is accessed via an attribute in a Web IDL interface, the attribute itself would be omitted from the objects that implement that interface — leaving the attribute on the object but making it return null or throw an exception is insufficient.
This specification relies on several other underlying specifications.
Many fundamental concepts from HTML are used by this specification. [HTML]
The IDL blocks in this specification use the semantics of the WebIDL specification. [WEBIDL]
The construction "a Foo
object", where
Foo
is actually an interface, is sometimes
used instead of the more accurate "an object implementing the
interface Foo
".
The term DOM is used to refer to the API set made available to
scripts in Web applications, and does not necessarily imply the
existence of an actual Document
object or of any other
Node
objects as defined in the DOM specifications. [DOM]
An IDL attribute is said to be getting when its value is being retrieved (e.g. by author script), and is said to be setting when a new value is assigned to it.
MessageEvent
interfacesMessages in server-sent events, Web sockets, cross-document
messaging, channel messaging, and broadcast channels use the
MessageEvent
interface for their message
events:
[Constructor(DOMString type, optional MessageEventInit eventInitDict), Exposed=(Window,Worker)] interface MessageEvent : Event { readonly attribute any data; readonly attribute DOMString origin; readonly attribute DOMString lastEventId; readonly attribute (WindowProxy or MessagePort)? source; readonly attribute MessagePort[]? ports; void initMessageEvent(DOMString typeArg, boolean canBubbleArg, boolean cancelableArg, any dataArg, DOMString originArg, DOMString lastEventIdArg, (WindowProxy or MessagePort) sourceArg, sequence<MessagePort>? portsArg); }; dictionary MessageEventInit : EventInit { any data; DOMString origin; DOMString lastEventId; (WindowProxy or MessagePort)? source; sequence<MessagePort> ports; };
data
Returns the data of the message.
origin
Returns the origin of the message, for server-sent events and cross-document messaging.
lastEventId
Returns the last event ID string, for server-sent events.
source
Returns the WindowProxy
of the source window, for cross-document
messaging, and the MessagePort
being attached, in the connect
event fired at
SharedWorkerGlobalScope
objects.
ports
Returns the MessagePort
array sent with the message, for cross-document
messaging and channel messaging.
Open Bugs 27128
The data
attribute must return the value
it was initialised to. When the object is created, this attribute must be initialised to null. It
represents the message being sent.
The origin
attribute must return the
value it was initialised to. When the object is created, this attribute must be initialised to the
empty string. It represents, in server-sent events and cross-document
messaging, the origin of the document that sent the message (typically the
scheme, hostname, and port of the document, but not its path or fragment identifier).
The lastEventId
attribute must
return the value it was initialised to. When the object is created, this attribute must be
initialised to the empty string. It represents, in server-sent events, the last event ID string of the event source.
The source
attribute must return the
value it was initialised to. When the object is created, this attribute must be initialised to
null. It represents, in cross-document messaging, the WindowProxy
of the
browsing context of the Window
object from which the message came; and
in the connect
events used by shared workers, the newly connecting
MessagePort
.
The ports
attribute must return the
value it was initialised to. When the object is created, this attribute must be initialised to
null. It represents, in
cross-document messaging and channel messaging, the
MessagePort
array being sent, if any.
The initMessageEvent()
method must initialise the event in a manner analogous to the similarly-named initEvent()
method. [DOM]
Web browsers, for security and privacy reasons, prevent documents in different domains from affecting each other; that is, cross-site scripting is disallowed.
While this is an important security feature, it prevents pages from different domains from communicating even when those pages are not hostile. This section introduces a messaging system that allows documents to communicate with each other regardless of their source domain, in a way designed to not enable cross-site scripting attacks.
The task source for the tasks in cross-document messaging is the posted message task source.
This section is non-normative.
For example, if document A contains an iframe
element that contains document B,
and script in document A calls postMessage()
on the
Window
object of document B, then a message event will be fired on that object,
marked as originating from the Window
of document A. The script in document A might
look like:
var o = document.getElementsByTagName('iframe')[0]; o.contentWindow.postMessage('Hello world', 'http://b.example.org/');
To register an event handler for incoming events, the script would use addEventListener()
(or similar mechanisms). For example, the script in document B
might look like:
window.addEventListener('message', receiver, false); function receiver(e) { if (e.origin == 'http://example.com') { if (e.data == 'Hello world') { e.source.postMessage('Hello', e.origin); } else { alert(e.data); } } }
This script first checks the domain is the expected domain, and then looks at the message, which it either displays to the user, or responds to by sending a message back to the document which sent the message in the first place.
Use of this API requires extra care to protect users from hostile entities abusing a site for their own purposes.
Authors should check the origin
attribute to
ensure that messages are only accepted from domains that they expect to receive messages from.
Otherwise, bugs in the author's message handling code could be exploited by hostile sites.
Furthermore, even after checking the origin
attribute, authors should also check that the data in question is of the expected format.
Otherwise, if the source of the event has been attacked using a cross-site scripting flaw, further
unchecked processing of information sent using the postMessage()
method could result in the attack being
propagated into the receiver.
Authors should not use the wildcard keyword (*) in the targetOrigin argument in messages that contain any confidential information, as otherwise there is no way to guarantee that the message is only delivered to the recipient to which it was intended.
Authors who accept messages from any origin are encouraged to consider the risks of a denial-of-service attack. An attacker could send a high volume of messages; if the receiving page performs expensive computation or causes network traffic to be sent for each such message, the attacker's message could be multplied into a denial-of-service attack. Authors are encouraged to employ rate limiting (only accepting a certain number of messages per minute) to make such attacks impractical.
The integrity of this API is based on the inability for scripts of one origin to
post arbitrary events (using dispatchEvent()
or otherwise) to objects in
other origins (those that are not the same).
Implementors are urged to take extra care in the implementation of this feature. It allows authors to transmit information from one domain to another domain, which is normally disallowed for security reasons. It also requires that UAs be careful to allow access to certain properties but not others.
User agents are also encouraged to consider rate-limiting message traffic between different origins, to protect naïve sites from denial-of-service attacks.
postMessage
(message, targetOrigin [, transfer ] )Posts a message to the given window. Messages can be structured objects, e.g. nested objects
and arrays, can contain JavaScript values (strings, numbers, Date
objects, etc), and can
contain certain data objects such as File
Blob
, FileList
,
and ArrayBuffer
objects.
Objects listed in transfer are transferred, not just cloned, meaning that they are no longer usable on the sending side.
If the origin of the target window doesn't match the given origin, the message is discarded,
to avoid information leakage. To send the message to the target regardless of origin, set the
target origin to "*
". To restrict the message to same-origin targets only,
without needing to explicitly state the origin, set the target origin to "/
".
Throws a DataCloneError
exception if transfer array contains
duplicate objects or if message could not be cloned.
When posting a message to a Window
of a browsing context
that has just been navigated to a new Document
is likely to result in the message not
receiving its intended recipient: the scripts in the target browsing context have to
have had time to set up listeners for the messages. Thus, for instance, in situations where a
message is to be sent to the Window
of newly created child iframe
,
authors are advised to have the child Document
post a message to their parent
announcing their readiness to receive messages, and for the parent to wait for this message before
beginning posting messages.
Open Bugs 18242
When a script invokes the postMessage(message, targetOrigin, transfer)
method (with two or three arguments) on a
Window
object, the user agent must follow these steps:
If the value of the targetOrigin argument is neither a single U+002A
ASTERISK character (*), a single U+002F SOLIDUS character (/), nor an absolute URL,
then throw a SyntaxError
exception and abort the overall set of steps.
Let new ports be an empty array.
Let transfer map be an empty association list of
Transferable
objects to placeholder objects.
If the method was invoked with a third argument transfer, run these substeps:
If any object is listed in transfer more than once, or any of the
Transferable
objects listed in transfer are marked as neutered, then throw a
DataCloneError
exception and abort these steps.
For each object x in transfer in turn, add a
mapping from x to a new unique placeholder object created for x to transfer map, and if x is a
MessagePort
object, also append the placeholder object to the new
ports array.
Let message clone be the result of obtaining a structured clone of the message argument, with transfer map as the transfer map. If this throws an exception, then throw that exception and abort these steps.
If the method was invoked with a third argument transfer, run these substeps:
Let new owner be the environment settings object of the
Window
object on which the method was invoked.
For each object x in transfer in turn, obtain a new object y by transferring the object x to new owner, and replace the placeholder object that was created for the object x by the new object y wherever the placeholder exists (i.e. in message clone and in new ports).
Make new ports into a read only array.
Return from the postMessage()
method, but in parallel continue running these steps.
If the targetOrigin argument is a single literal U+002F SOLIDUS
character (/), and the Document
of the Window
object on which the
method was invoked does not have the same origin as the responsible
document specified by the entry settings object, then abort these steps
silently.
Otherwise, if the targetOrigin argument is an absolute URL,
and the Document
of the Window
object on which the method was invoked
does not have the same origin as targetOrigin, then abort
these steps silently.
Otherwise, the targetOrigin argument is a single literal U+002A ASTERISK character (*), and no origin check is made.
Create a trusted event that uses the
MessageEvent
interface, with the event type message
, which does not bubble, is not cancelable, and has no
default action. The data
attribute must be
initialised to the value of message clone, the origin
attribute must be initialised to the Unicode serialisation of the
origin specified by the incumbent settings object, the source
attribute must be initialised to the
WindowProxy
object corresponding to the global object (a
Window
object) specified by the incumbent settings object, and the
ports
attribute must be initialised to the new ports array.
Queue a task to dispatch the
event created in the previous step at the Window
object on which the method was
invoked. The task source for this task is the
posted message task source.
This section is non-normative.
To enable independent pieces of code (e.g. running in different browsing contexts) to communicate directly, authors can use channel messaging.
Communication channels in this mechanism are implemented as two-ways pipes, with a port at each end. Messages sent in one port are delivered at the other port, and vice-versa. Messages are delivered as DOM events, without interrupting or blocking running tasks.
To create a connection (two "entangled" ports), the MessageChannel()
constructor is called:
var channel = new MessageChannel();
One of the ports is kept as the local port, and the other port is sent to the remote code, e.g.
using postMessage()
:
otherWindow.postMessage('hello', 'http://example.com', [channel.port2]);
To send messages, the postMessage()
method on
the port is used:
channel.port1.postMessage('hello');
To receive messages, one listens to message
events:
channel.port1.onmessage = handleMessage; function handleMessage(event) { // message is in event.data // ... }
Data sent on a port can be structured data; for example here an array of strings is passed on a
MessagePort
:
port1.postMessage(['hello', 'world']);
This section is non-normative.
In this example, two JavaScript libraries are connected to each other using
MessagePort
s. This allows the libraries to later be hosted in different frames, or
in Worker
objects, without any change to the APIs.
<script src="contacts.js"></script> <!-- exposes a contacts object --> <script src="compose-mail.js"></script> <!-- exposes a composer object --> <script> var channel = new MessageChannel(); composer.addContactsProvider(channel.port1); contacts.registerConsumer(channel.port2); </script>
Here's what the "addContactsProvider()" function's implementation could look like:
function addContactsProvider(port) { port.onmessage = function (event) { switch (event.data.messageType) { 'search-result': handleSearchResult(event.data.results); break; 'search-done': handleSearchDone(); break; 'search-error': handleSearchError(event.data.message); break; // ... } }; };
Alternatively, it could be implemented as follows:
function addContactsProvider(port) { port.addEventListener('message', function (event) { if (event.data.messageType == 'search-result') handleSearchResult(event.data.results); }); port.addEventListener('message', function (event) { if (event.data.messageType == 'search-done') handleSearchDone(); }); port.addEventListener('message', function (event) { if (event.data.messageType == 'search-error') handleSearchError(event.data.message); }); // ... port.start(); };
The key difference is that when using addEventListener()
, the start()
method must also be invoked. When using onmessage
, the call to start()
is implied.
The start()
method, whether called explicitly or
implicitly (by setting onmessage
), starts the
flow of messages: messages posted on message ports are initially paused, so that they don't get
dropped on the floor before the script has had a chance to set up its handlers.
This section is non-normative.
Ports can be viewed as a way to expose limited capabilities (in the object-capability model sense) to other actors in the system. This can either be a weak capability system, where the ports are merely used as a convenient model within a particular origin, or as a strong capability model, where they are provided by one origin provider as the only mechanism by which another origin consumer can effect change in or obtain information from provider.
For example, consider a situation in which a social Web site embeds in one iframe
the user's e-mail contacts provider (an address book site, from a second origin), and in a second
iframe
a game (from a third origin). The outer social site and the game in the second
iframe
cannot access anything inside the first iframe
; together they can
only:
iframe
to a new URL, such as the same
URL but with a different fragment identifier, causing the Window
in the
iframe
to receive a hashchange
event.iframe
, causing the Window
in the iframe
to
receive a resize
event.message
event to the Window
in the
iframe
using the window.postMessage()
API.The contacts provider can use these methods, most particularly the third one, to provide an API
that can be accessed by other origins to manipulate the user's address book. For example, it could
respond to a message "add-contact Guillaume Tell
<EMAIL_ADDRESS>" by adding the given person and e-mail address to the user's
address book.
To avoid any site on the Web being able to manipulate the user's contacts, the contacts provider might only allow certain trusted sites, such as the social site, to do this.
Now suppose the game wanted to add a contact to the user's address book, and that the social site was willing to allow it to do so on its behalf, essentially "sharing" the trust that the contacts provider had with the social site. There are several ways it could do this; most simply, it could just proxy messages between the game site and the contacts site. However, this solution has a number of difficulties: it requires the social site to either completely trust the game site not to abuse the privilege, or it requires that the social site verify each request to make sure it's not a request that it doesn't want to allow (such as adding multiple contacts, reading the contacts, or deleting them); it also requires some additional complexity if there's ever the possibility of multiple games simultaneously trying to interact with the contacts provider.
Using message channels and MessagePort
objects, however, all of these problems can
go away. When the game tells the social site that it wants to add a contact, the social site can
ask the contacts provider not for it to add a contact, but for the capability to add a
single contact. The contacts provider then creates a pair of MessagePort
objects, and
sends one of them back to the social site, who forwards it on to the game. The game and the
contacts provider then have a direct connection, and the contacts provider knows to only honor a
single "add contact" request, nothing else. In other words, the game has been granted the
capability to add a single contact.
This section is non-normative.
Continuing the example from the previous section, consider the contacts provider in particular.
While an initial implementation might have simply used XMLHttpRequest
objects in the
service's iframe
, an evolution of the service might instead want to use a shared worker with a single WebSocket
connection.
If the initial design used MessagePort
objects to grant capabilities, or even just
to allow multiple simultaneous independent sessions, the service implementation can switch from
the XMLHttpRequest
s-in-each-iframe
model to the
shared-WebSocket
model without changing the API at all: the ports on the service
provider side can all be forwarded to the shared worker without it affecting the users of the API
in the slightest.
[Constructor, Exposed=(Window,Worker)] interface MessageChannel { readonly attribute MessagePort port1; readonly attribute MessagePort port2; };
MessageChannel
()Returns a new MessageChannel
object with two new MessagePort
objects.
port1
Returns the first MessagePort
object.
port2
Returns the second MessagePort
object.
When the MessageChannel()
constructor is
called, it must run the following algorithm:
Create a new MessagePort
object whose owner is the incumbent settings object, and let
port1 be that object.
Create a new MessagePort
object whose owner is the incumbent settings object, and let
port2 be that object.
Entangle the port1 and port2 objects.
Instantiate a new MessageChannel
object, and let channel
be that object.
Let the port1
attribute of the channel object be port1.
Let the port2
attribute of the channel object be port2.
Return channel.
The port1
and port2
attributes must return the values they were
assigned when the MessageChannel
object was created.
Each channel has two message ports. Data sent through one port is received by the other port, and vice versa.
[Exposed=(Window,Worker)] interface MessagePort : EventTarget { void postMessage(any message, optional sequence<Transferable> transfer); void start(); void close(); // event handlers attribute EventHandler onmessage; }; // MessagePort implements Transferable;
postMessage
(message [, transfer] )Posts a message through the channel. Objects listed in transfer are transferred, not just cloned, meaning that they are no longer usable on the sending side.
Throws a DataCloneError
exception if transfer array contains
duplicate objects or the source or target ports, or if message could not be
cloned.
start
()Begins dispatching messages received on the port.
close
()Disconnects the port, so that it is no longer active.
Each MessagePort
object can be entangled with another (a symmetric relationship).
Each MessagePort
object also has a task source called the port
message queue, initially empty. A port message queue can be enabled or
disabled, and is initially disabled. Once enabled, a port can never be disabled again (though
messages in the queue can get moved to another queue or removed altogether, which has much the
same effect). A MessagePort
also has a has been shipped flag, which must
initially be false, and an owner, which is a settings
object set when the object is created, as described below.
When a port's port message queue is enabled, the event loop must use it as one of its task sources. When a port's owner specifies a responsible event loop that is a browsing context event loop, all tasks queued on its port message queue must be associated with the responsible document specified by the port's owner.
If the port's owner specifies a responsible document that is fully active, but the event listeners all have scripts whose settings objects specify responsible documents that are not fully active, then the messages will be lost.
Each event loop has a task source called the unshipped port
message queue. This is a virtual task source: it must act as if it contained
the tasks of each port message queue of each
MessagePort
whose has been shipped flag is false, whose port
message queue is enabled, and whose owner
specifies that event loop as the responsible event loop, in the order in
which they were added to their respective task source. When a task would be removed from the unshipped port message
queue, it must instead be removed from its port message queue.
When a MessagePort
's has been shipped flag is false, its port
message queue must be ignored for the purposes of the event loop. (The
unshipped port message queue is used instead.)
The has been shipped flag is set to true when a port, its twin, or
the object it was cloned from, is or has been transferred. When a MessagePort
's has been shipped flag
is true, its port message queue acts as a first-class task source,
unaffected to any unshipped port message queue.
When the user agent is to create a new MessagePort
object with a
particular settings object as its owner, it must instantiate a
new MessagePort
object, and let its owner be
owner.
When the user agent is to entangle two MessagePort
objects, it must run
the following steps:
If one of the ports is already entangled, then disentangle it and the port that it was entangled with.
If those two previously entangled ports were the two ports of a
MessageChannel
object, then that MessageChannel
object no longer
represents an actual channel: the two ports in that object are no longer entangled.
Associate the two ports to be entangled, so that they form the two parts of a new channel.
(There is no MessageChannel
object that represents this channel.)
Two ports A and B that have gone through this step are now said to be entangled; one is entangled to the other, and vice versa.
While this specification describes this process as instantaneous, implementations are more likely to implement it via message passing. As with all algorithms, the key is "merely" that the end result be indistinguishable, in a black-box sense, from the specification.
When the user agent is to clone a port original port, with the
clone being owned by owner, it must run the following steps, which return a
new MessagePort
object. These steps must be run atomically.
Set original port's has been shipped flag to true.
Create a new MessagePort
object whose owner is owner, and let new port be that object.
Set new port's has been shipped flag to true.
Move all the tasks that are to fire message
events in the port message queue of original port to the port message queue of new
port, if any, leaving the new port's port message queue
in its initial disabled state, and, if the new port's owner specifies a responsible event loop that is
a browsing context event loop, associating the moved tasks with the responsible document specified by new port's owner.
If the original port is entangled with another port, then run these substeps:
Let the remote port be the port with which the original port is entangled.
Set remote port's has been shipped flag to true.
Entangle the remote port and new port objects. The original port object will be disentangled by this process.
Return new port. It is the clone.
To transfer a
MessagePort
object old to a new owner owner,
a user agent must clone the old object with
the clone being owned by owner, thus obtaining new, must
neuter the old port, and
must finally return new.
The postMessage()
method, when
called on a port source port, must cause the user agent to run the following
steps:
Let target port be the port with which source port is entangled, if any.
Let doomed be false. It is set to true if a condition is detected that will make this message cause the port to be unusable; specifically, if the message contains target port as one of the objects being transferred. (This condition cannot necessarily be detected when the method is called.)
Let new ports be an empty array.
Let transfer map be an empty association list of
Transferable
objects to placeholder objects.
If the method was invoked with a second argument transfer, run these substeps:
If any object is listed in transfer more than once, or any of the
Transferable
objects listed in transfer are marked as neutered, then throw a
DataCloneError
exception and abort these steps.
If any of the objects in transfer are the source
port, then throw a DataCloneError
exception and abort these steps.
If any of the objects in transfer are the target port, if any, then let doomed be true, and optionally report to a developer console that the target port was posted to itself, causing the communication channel to be lost.
For each object x in transfer in turn, add a
mapping from x to a new unique placeholder object created for x to transfer map, and if x is a
MessagePort
object, also append the placeholder object to the new
ports array.
Let message clone be the result of obtaining a structured clone of the message argument, with transfer map as the transfer map. If this throws an exception, then throw that exception and abort these steps.
If the method was invoked with a second argument transfer, run these substeps:
Let new owner be the owner of
target port, if there is a target port and doomed is false, or else some arbitrary owner. (This new
owner is used when transferring objects below. If there is no target
port, or if the target port is one of the objects being transferred, the Transferable
objects given in the second argument, if any, are still transferred, but since they are then discarded, it doesn't matter where they
are transferred to.)
For each object x in transfer in turn, obtain a new object y by transferring the object x to new owner, and replace the placeholder object that was created for the object x by the new object y wherever the placeholder exists (i.e. in message clone and in new ports).
Make new ports into a read only array.
If there is no target port (i.e. if source port is not entangled), or if doomed is true, then abort these steps.
Create an event e that uses the MessageEvent
interface, with the name message
, which does not bubble, is not cancelable, and has no
default action.
Let the data
attribute of e be
initialised to the value of message clone.
Let the ports
attribute of e be
initialised to the new ports array.
Add a task that runs the following steps to the port message queue of target port:
Let target be the MessagePort
in whose port message
queue the event e now finds itself.
Dispatch e at target.
The start()
method must enable its port's
port message queue, if it is not already enabled.
The close()
method, when called on a port
local port that is entangled with another port, must cause the user agent to
disentangle the two ports. If the method is called on a port that is not entangled, then the
method must do nothing.
The following are the event handlers (and their corresponding event handler event types) that must be supported, as event
handler IDL attributes, by all objects implementing the MessagePort
interface:
| Event handler | Event handler event type |
|---|---|
onmessage | message
|
The first time a MessagePort
object's onmessage
IDL attribute is set, the port's port
message queue must be enabled, as if the start()
method had been called.
The API described in this section is controversial, as, in an attempt to solve an architectural memory leak, it instead exposes the details of Garbage Collection. This is a lose-lose scenario. A better solution is really needed here.
Broadcasting to many ports is in principle relatively simple: keep an array of
MessagePort
objects to send messages to, and iterate through the array to send a
message. However, this has one rather unfortunate effect: it prevents the ports from being garbage
collected, even if the other side has gone away.
To avoid this problem, the PortCollection
object can be used. It acts as an opaque
array of MessagePort
objects, thus allowing the objects to be garbage collected when
they stop being relevant, while still allowing scripts to iterate over the
MessagePort
objects.
[Constructor, Exposed=(Window,Worker)] interface PortCollection { void add(MessagePort port); void remove(MessagePort port); void clear(); void iterate(PortCollectionCallback callback); }; callback PortCollectionCallback = void (MessagePort port);
PortCollection
()Returns a new empty PortCollection
object.
add
(port)Adds port to the collection, if it isn't already present.
remove
(port)Removes port from the collection, if it is present.
clear
()Removes all ports from the collection.
iterate
(callback)Calls callback for each port in the collection.
A PortCollection
object has an initially empty list of ports. When a MessagePort
object in
a list of ports is garbage collected, it must be
silently removed from that list of ports. Objects
in a list of ports are ordered chronologically by
the time at which they were most recently added; the least-recently added MessagePort
object is the first in the list, and the most-recently added MessagePort
is the last
in the list.
The PortCollection()
constructor must return
a new PortCollection
object (with an empty list of ports).
The add()
method must add the
MessagePort
given by the argument to the PortCollection
object's list of ports, unless the MessagePort
is
already in the list of ports, in which case the
method does nothing. (Calling this method with a port already in the list does not move the port
to the end of the list.)
The remove()
method must remove the
MessagePort
given by the argument from the PortCollection
object's list of ports, unless the MessagePort
is
not in the list of ports, in which case the
method does nothing.
The clear()
method must remove all
MessagePort
objects from the PortCollection
object's list of ports, returning it to the initial empty state.
If the list of ports is already empty, the method
does nothing.
The iterate()
method must invoke its
PortCollectionCallback
argument once for each MessagePort
object in the
object's list of ports, in the order defined
above, with each invocation being passed the corresponding MessagePort
object as the
callback's sole argument.
When a MessagePort
object o is entangled, user agents must
either act as if o's entangled MessagePort
object has a strong
reference to o, or as if the global object specified by o's owner has a strong reference to o.
Thus, a message port can be received, given an event listener, and then forgotten, and so long as that event listener could receive a message, the channel will be maintained.
Of course, if this was to occur on both sides of the channel, then both ports could be garbage collected, since they would not be reachable from live code, despite having a strong reference to each other.
Furthermore, a MessagePort
object must not be garbage collected while there exists
an event referenced by a task in a task queue that is to be dispatched on that MessagePort
object, or while the MessagePort
object's port message queue is enabled
and not empty.
There are no strong references from a PortCollection
object to its
MessagePort
objects. (That is in fact the whole point of PortCollection
objects: they allow for MessagePort
objects to be referenced without preventing them
from being garbage collected.)
Authors are strongly encouraged to explicitly close MessagePort
objects to disentangle them, so that their resources can be recollected. Creating many
MessagePort
objects and discarding them without closing them can lead to high
transient memory usage since garbage collection is not necessarily performed promptly, especially
for MessagePort
s where garbage collection can involve cross-process coordination.
All references are normative unless marked "Non-normative".
For a full list of acknowledgements, please see the WHATWG HTML standard.


Before Change
best_index = -1
// history_results is sorted by (model_id, partial_fit_calls)
// best is the model_id with the highest partial fit calls
for k, v in itertools.groupby(history_results, key=key):
v = list(v)
best_index += len(v)
if k == best_model_id:
break
return results.models[best_model_id], best_index
def _process_results(self, results):
Called with the output of `fit` immediately after it finishes.
After Change
// Could use max(scores, key=score.get), but what if score is repeated?
// Happens in the test case a lot
model_ids = list(scores.keys())
scores = [scores[k] for k in model_ids]
model_idx = np.argmax(scores)
best_model_id = model_ids[model_idx]
best_est = results.models[best_model_id]
idx = cv_results["model_id"] == best_model_id
assert idx.sum() == 1
best_idx = np.argmax(idx)
return best_idx, best_est
def _process_results(self, results):
Called with the output of `fit` immediately after it finishes.


Audio of the user
Avatar of the user
Whether the user is starting the video
Display name
Whether the user is host
Whether the user is host
Whether the audio is muted
Whether the user is starting share
Whether the sharing is paused
Identify of the user
Generated using TypeDoc
Interface of Participant Properties


The information on this page is NOT an official record. Do not rely on the correctness or completeness of this information. Verify all information with the official record keeper. The information contained in this report is provided in compliance with the Oklahoma Open Records Act, 51 O.S. 24A.1. Use of this information is governed by this act, as well as other applicable state and federal laws.
| STATE OF OKLAHOMA, Plaintiff, v. SHANTAL TEAIRRA WARD, Defendant. |
No. CF-2015-2603 (Criminal Felony) Filed: 04/09/2015 Closed: 10/03/2018 Judge: Henderson, Timothy R |
DEL CITY PD,
ARRESTING AGENCY
STATE OF OKLAHOMA,
Plaintiff
WARD, SHANTAL TEAIRRA,
Defendant
None
| Event | Party | Docket | Reporter |
|---|---|---|---|
|
Thursday, April 30, 2015 at 1:30 PM PRELIMINARY HEARING CONFERENCE |
WARD, SHANTAL TEAIRRA | D. Fred Doak | |
|
Thursday, June 4, 2015 at 9:00 AM PRELIMINARY HEARING CONFERENCE X 2 THA X 1 (DEFT WAS LATE) |
WARD, SHANTAL TEAIRRA | D. Fred Doak | |
|
Wednesday, July 8, 2015 at 9:00 AM PRELIMINARY HEARING CONFERENCE X 3 THA X 2 |
WARD, SHANTAL TEAIRRA | D. Fred Doak | |
|
Wednesday, August 5, 2015 at 0:00 AM REVIEW BOND FORFEITURE 1 |
WARD, SHANTAL TEAIRRA | ||
|
Friday, October 23, 2015 at 0:00 AM REVIEW BOND FORFEITURE 2 |
WARD, SHANTAL TEAIRRA | ||
|
Monday, November 9, 2015 at 9:00 AM PRETRIAL CONFERENCE |
WARD, SHANTAL TEAIRRA | Timothy R Henderson | |
|
Monday, January 25, 2016 at 9:01 AM ARRAIGNMENT; FTA-PTC |
WARD, SHANTAL TEAIRRA | Timothy R Henderson | |
|
Friday, February 19, 2016 at 9:00 AM PRETRIAL CONFERENCE; PREV FTA |
WARD, SHANTAL TEAIRRA | Timothy R Henderson | |
|
Monday, February 29, 2016 at 0:00 AM REVIEW BOND FORFEITURE 2 (STRICKEN) |
WARD, SHANTAL TEAIRRA | ||
|
Tuesday, March 8, 2016 at 0:00 AM REVIEW BOND FORFEITURE 1 (STRICKEN) |
WARD, SHANTAL TEAIRRA | ||
|
Wednesday, February 26, 2020 at 1:30 PM RULE 8 HEARING |
WARD, SHANTAL TEAIRRA | April Collins |
Parties appear only under the counts with which they were charged. For complete sentence information, see the court minute on the docket.
| Count # 1. |
Count as Filed:
LMFR, GRAND LARCENY,
in violation of 21 O.S. 1701-1708,1731 Date of Offense: 03/30/2015 |
| Party Name | Disposition Information | |
|---|---|---|
|
Disposed: DEFERRED,
02/11/2016.
Guilty Plea Count as Disposed: GRAND LARCENY(LMFR) Violation of 21 O.S. 1701-1708,1731 |
||
|
Disposed: CONVICTION,
10/03/2018.
Guilty Plea Count as Disposed: LARCENY OF MERCHANDISE FROM A RETAILER (OVER $500 LESS THAN $1,000)(LMFR) Violation of 21 O.S. 1701-1708,1731 |
| Date | Code | Description | Count | Party | Amount |
|---|---|---|---|---|---|
|
|
|
CRIMINAL FELONY INITIAL FILING. Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
COVER SHEET Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
DEFENDANT SHANTAL TEAIRRA WARD WAS CHARGED WITH COUNT #1, GRAND LARCENY IN VIOLATION OF 21 O.S. 1701-1708,1731 |
1 | WARD, SHANTAL TEAIRRA | |
|
|
|
DEFENDANT SHANTAL TEAIRRA WARD WAS CHARGED WITH COUNT #1, GRAND LARCENY IN VIOLATION OF 21 O.S. 1701-1708,1731 |
1 | WARD, SHANTAL TEAIRRA | |
|
|
|
OCIS HAS AUTOMATICALLY ASSIGNED JUDGE HENDERSON, TIMOTHY R TO THIS CASE. |
|||
|
|
|
WARRANT OF ARREST ISSUED, JUDGE: RUSSELL HALL - BOND AMOUNT: $2,000.00 |
WARD, SHANTAL TEAIRRA | $ 50.00 | |
|
|
|
OKLAHOMA COURT INFORMATION SYSTEM REVOLVING FUND |
WARD, SHANTAL TEAIRRA | $ 25.00 | |
|
|
|
JUDGE HALL: DEFT APPEARS IN PERSON, IN CUSTODY, W/OUT COUNSEL. PUBLIC DEFENDER TENTATIVELY APPOINTED. STATE NOT PRESENT. DEFT WAIVES READING OF INFORMATION AND ENTERS A PLEA OF NOT GUILTY. MATTER SET FOR PRELIMINARY HEARING CONFERENCE ON 4-30-15 AT 1:30 PM BEFORE JUDGE DOAK. BAIL SET AT $2,000 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
JUDGE DOAK: COMES ON FOR PHC. DEFENDANT APPEARS IN PERSON W/OUT COUNSEL. PHC CONT TO 6-4-15 AT 9 AM BEFORE JUDGE DOAK BY COURT TO HIRE COUNSEL Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
PROFESSIONAL BOND FOR WARD, SHANTAL TEAIRRA POSTED BY JONES, ANGELA (MULTICOUNTY AGENT:PLETCHER, CURT ) (POWER NUMBER:72079 ), IN THE AMOUNT OF $2,000.00, POSTED 04/06/2015 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | $ 10.00 | |
|
|
|
BOND INITIAL FILING JAIL FUND FEE |
WARD, SHANTAL TEAIRRA | $ 25.00 | |
|
|
|
COURT CLERK ADMINISTRATIVE FEE ON $25 COLLECTIONS |
WARD, SHANTAL TEAIRRA | $ 2.50 | |
|
|
|
WARRANT RETURNED 5/5/2015, WARRANT ISSUED ON 4/10/2015 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
JUDGE DOAK: COMES ON FOR PHC. DEFENDANT APPEARS IN PERSON W/OUT COUNSEL. STATE PRESENT BY ADA KEMP. PHC CONT TO 7-8-15 AT 9 AM BEFORE JUDGE DOAK BY COURT TO HIRE COUNSEL Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
JUDGE DOAK: COMES ON FOR PHC. DEFENDANT FAILS TO APPEAR. BOND ORDERED FORFEITED. ALIAS WARRANT TO ISSUE. ALIAS WARRANT ISSUED. BAIL SET AT $4,000 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
THE STATUS OF THE BOND ENTRY DETAILED IN DOCKET SERIAL #82554644 ABOVE HAS CHANGED TO READ AS FOLLOWS: |
WARD, SHANTAL TEAIRRA | ||
|
|
|
BENCH WARRANT ISSUED FAILED TO APPEAR, JUDGE: D. DOAK - BOND AMOUNT: $4,000.00 |
WARD, SHANTAL TEAIRRA | $ 50.00 | |
|
|
|
OKLAHOMA COURT INFORMATION SYSTEM REVOLVING FUND |
WARD, SHANTAL TEAIRRA | $ 25.00 | |
|
|
|
ORDER & JUDGMENT OF FORFEITURE- CERTIFIED COPY BY CERTIFIED MAIL TO: ANGELA JONES AND CURT PLETCHER/$2,000/JUDGE DOAK Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
HENDERSON: ALIAS WARRANT ISSUED IS RECALLED. BOND FORFEITURE SET ASIDE. BOND REINSTATED. CASE RESET FOR PTC 11-09-15,9AM; DEFT WAIVES PH, JURISDICTON; ATTY J. JONES |
WARD, SHANTAL TEAIRRA | ||
|
|
|
WAIVER OF PRELIMINARY HEARING AND BIND- OVER ORDER; JUDGE HENDERSON Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
JUDGE HENDERSON: MOTION AND ORDER SETTING ASIDE/VACATING BOND FORFEITURE, RECALLING WARRANT, REINSTATING BOND BY ANGELA JONES AND RESETTING CAUSE ON DOCKET Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
|
WARD, SHANTAL TEAIRRA | ||
|
|
|
WARRANT RETURNED 7/21/2015, WARRANT ISSUED ON 7/13/2015 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
RECEIPT FOR CERTIFIED MAIL-CURT PLETCHER-CURT PLETCHER SIGNED ON 7/24/15. |
WARD, SHANTAL TEAIRRA | $ 10.00 | |
|
|
|
FRECEIPT FOR CERTIFIED MAIL" ANGELA JONES-SIGNED BY ANGELA JONES GRREN CARD NOT DATED ACCORDING TO USPS ITEM WAS DELIVERED ON. |
WARD, SHANTAL TEAIRRA | $ 10.00 | |
|
|
|
BOND FORFEITURE FILED ON 7-8-15 REVIEWED THIS DATE. RECORD REFLECTS BOND FORFEITURE WAS SET ASIDE AND BOND REINSTATED ON 7-20-15. FORFEITURE PROCEEDINGS CONCLUDED, NO FURTHER REVIEW NEEDED. |
WARD, SHANTAL TEAIRRA | ||
|
|
|
HENDERSON: DEFT FAILED TO APPEAR FOR PTC. BOND FORFEITED. ALIAS WARRANT TO ISSUE. BOND DENIED Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
BOND FORFEITED |
WARD, SHANTAL TEAIRRA | ||
|
|
|
BENCH WARRANT ISSUED FAILED TO APPEAR, JUDGE: TIMOTHY HENDERSON - BOND AMOUNT: |
WARD, SHANTAL TEAIRRA | $ 50.00 | |
|
|
|
OKLAHOMA COURT INFORMATION SYSTEM REVOLVING FUND |
WARD, SHANTAL TEAIRRA | $ 25.00 | |
|
|
|
ORDER & JUDGMENT OF FORFEITURE- CERTIFIED COPY BY CERTIFIED MAIL TO: ANGELA JONES AND CURT PLETCHER/$2,000/JUDGE HENDERSON Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
RECEIPT FOR CERTIFIED MAIL-CURT PLETCHER-CURT PLETCHER SIGNED ON 11/30/15. |
WARD, SHANTAL TEAIRRA | $ 10.00 | |
|
|
|
RECEIPT FOR CERTIFIED MAIL-ANGELA JONES-ANGELA JONES SIGNED ON 12/8/15. |
WARD, SHANTAL TEAIRRA | $ 10.00 | |
|
|
|
WARRANT RETURNED 1/21/2016, WARRANT ISSUED ON 11/13/2015 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
HENDERSON: DEFT ARRAIGNED ON FTA WARRANT. PTC RESET 02-19-16,9AM; BOND $4,000. NO ATTY |
WARD, SHANTAL TEAIRRA | ||
|
|
|
THE STATUS OF THE BOND ENTRY DETAILED IN DOCKET SERIAL #82554644 ABOVE HAS CHANGED TO READ AS FOLLOWS: |
WARD, SHANTAL TEAIRRA | ||
|
|
|
CORRECTIONS TO ACCOUNTING ENTRIES FOR INITIAL BOND FILING. |
WARD, SHANTAL TEAIRRA | $ -25.00 | |
|
|
|
CORRECTIONS TO ACCOUNTING ENTRIES FOR INITIAL BOND FILING. |
WARD, SHANTAL TEAIRRA | $ -2.50 | |
|
|
|
CORRECTIONS TO ACCOUNTING ENTRIES FOR INITIAL BOND FILING. |
WARD, SHANTAL TEAIRRA | $ 25.00 | |
|
|
|
CLERK'S BOND FORFEITURE MINUTE Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
BOND FORFEITURE FILED ON 11/9/15 REVIEWED THIS DATE. RECORD REFLECTS THAT THE DEFENDANT WAS REARRAIGNED ON 1/25/16. FORFEITURE PROCEEDINGS CONCLUDED, NO FURTHER REVIEW NEEDED. |
WARD, SHANTAL TEAIRRA | ||
|
|
|
JUDGE DOAK: COMES ON FOR PLEA. DEFENDANT APPEARS IN PERSON, IN CUSTODY W/COUNSEL R. HULL, PD. STATE PRESENT BY ADA J. SALMON. DEFT ENTERS A PLEA OF GUILTY AND SENTENCING IS DEFERRED UNTIL FEBRUARY 10, 2021 (5) YRS, DEFT SHALL SERVE [45] DAYS TO DO IN CO. JAIL W/CFTS. DEFT TO BE SUPERVISED BY DA. DEFT TO PAY $45 VCA, $200 CRT APT'D ATY FEE, $25 DA, $150 DNAAND COURT COSTS. ALL COSTS DUE INSTANTER. ANY BOND NOT IN FORFEITURE EXONERATED. COURT REPORTER WAIVED. RELEASE ISSUED. |
1 | WARD, SHANTAL TEAIRRA | |
|
|
|
COURT COSTS ON FELONY |
1 | WARD, SHANTAL TEAIRRA | $ 103.00 |
|
|
|
DA COUNCIL PROSECUTION ASSESSMENT FOR FELONY |
1 | WARD, SHANTAL TEAIRRA | $ 25.00 |
|
|
|
OKLAHOMA COURT INFORMATION SYSTEM REVOLVING FUND |
1 | WARD, SHANTAL TEAIRRA | $ 25.00 |
|
|
|
SHERIFF’S SERVICE FEE FOR COURT HOUSE SECURITY |
1 | WARD, SHANTAL TEAIRRA | $ 10.00 |
|
|
|
MEDICAL EXPENSE LIABILITY REVOLVING FUND |
1 | WARD, SHANTAL TEAIRRA | $ 10.00 |
|
|
|
CLEET PENALTY ASSESSMENT |
1 | WARD, SHANTAL TEAIRRA | $ 9.00 |
|
|
|
LAW LIBRARY FEE |
1 | WARD, SHANTAL TEAIRRA | $ 6.00 |
|
|
|
FORENSIC SCIENCE IMPROVEMENT ASSESSMENT |
1 | WARD, SHANTAL TEAIRRA | $ 5.00 |
|
|
|
SHERIFF'S SERVICE FEE ON ARRESTS |
1 | WARD, SHANTAL TEAIRRA | $ 5.00 |
|
|
|
AFIS FEE |
1 | WARD, SHANTAL TEAIRRA | $ 5.00 |
|
|
|
C.H.A.B. STATUTORY FEE |
1 | WARD, SHANTAL TEAIRRA | $ 3.00 |
|
|
|
ATTORNEY GENERAL VICTIM SERVICES UNIT |
1 | WARD, SHANTAL TEAIRRA | $ 3.00 |
|
|
|
DNA LAB FEE- - PAY TO OSBI |
1 | WARD, SHANTAL TEAIRRA | $ 150.00 |
|
|
|
ATTORNEY FEE - TULSA AND OKLAHOMA COUNTY PUBLIC DEFENDER |
1 | WARD, SHANTAL TEAIRRA | $ 200.00 |
|
|
|
VICTIMS COMPENSATION ASSESSMENT (AC12) |
1 | WARD, SHANTAL TEAIRRA | $ 45.00 |
|
|
|
COURT CLERK ADMINISTRATIVE FEE ON COLLECTIONS |
1 | WARD, SHANTAL TEAIRRA | $ 42.00 |
|
|
|
ISSUE COMMITMENT |
WARD, SHANTAL TEAIRRA | ||
|
|
|
PLEA OF GUILTY - SUMMARY OF FACTS Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
CAP FORM Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
ORDER OF THE COURT - RULE 8 HEARING Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
RULES AND CONDITIONS OF SUPERVISED PROBATION THROUGH THE OKLAHOMA COUNTY DISTRICT ATTORNEY'S OFFICE Document Unavailable (#1032214303) |
WARD, SHANTAL TEAIRRA | ||
|
|
|
SUPPLEMENTAL ORDER Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
TEMPORARY COMMITMENT W/SHERIFF'S RETURN Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
HENDERSON: DEFT PREV PLED |
WARD, SHANTAL TEAIRRA | ||
|
|
|
NOTICE OF GOOD BEHAVIOR CREDIT AND OR CREDIT FOR LABOR Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
CLAIM FOR INTERCEPT OF TAX REFUND |
WARD, SHANTAL TEAIRRA | ||
|
|
|
BENCH WARRANT ISSUED FAILED TO APPEAR AND PAY, JUDGE: DONALD EASTER - BOND AMOUNT: $1,333.80 |
WARD, SHANTAL TEAIRRA | $ 50.00 | |
|
|
|
CLERK'S BENCH WARRANT FEE {TITLE 22 O.S.966A} |
WARD, SHANTAL TEAIRRA | $ 5.00 | |
|
|
|
OKLAHOMA COURT INFORMATION SYSTEM REVOLVING FUND |
WARD, SHANTAL TEAIRRA | $ 25.00 | |
|
|
|
CASE SENT FOR COLLECTION. BATCH ID: 20161208-5815 - COLLECTION ID: 115211 |
WARD, SHANTAL TEAIRRA | $ 307.80 | |
|
|
|
REDUCTION IN BENCH WARRANT FEE TO SHERIFF (10%) |
WARD, SHANTAL TEAIRRA | $ -5.00 | |
|
|
|
ADDITION OF 10% FOR WARRANT COLLECTION |
WARD, SHANTAL TEAIRRA | $ 5.00 | |
|
|
|
WARRANT RETURNED 4/21/2017, WARRANT ISSUED ON 12/6/2016 Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
ORDER OF RELEASE W/SHERIFF'S RETURN- COST WARRANT ONLY Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
CLAIM FOR INTERCEPT OF TAX REFUND |
WARD, SHANTAL TEAIRRA | ||
|
|
|
CLAIM FOR INTERCEPT OF TAX REFUND |
WARD, SHANTAL TEAIRRA | ||
|
|
|
JUDGE HENDERSON: THE DEFENDANT APPEARS WITH ATTORNEY HOWARD MORROW. THE STATE APPEARS BY ADA JESSICA FOSTER. THE DEFENDANT ENTERS A NEGOTIATED PLEA OF GUILTY TO THE STATE'S APPLICATION TO ACCELERATE & THE DEFT IS SENTENCED TO: COUNT 1) 1 YEAR UNDER THE SUPERVISION OF OPS, LLC (1 YR S/S). RUNNING CONCURRENTLY WITH CF-2015-7177 & CF-2017-3104.  COURT REPORTER WAIVED. |
1 | WARD, SHANTAL TEAIRRA | |
|
|
|
PLEA OF GUILTY - SUMMARY OF FACTS ACCEL Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
ACCELERATION OF A DEFERRED SENTENCE JUDGMENT AND SENTENCE/ ELECTRONICALLY TRANSFERRED/ SUSPENDED/ JUDGE HENDERSON Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
APPLICATION TO REVOKE SUSPENDED SENTENCE Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
COST DOCKET ORDER JUDGE COLLINS Document Available at Court Clerk's Office |
WARD, SHANTAL TEAIRRA | ||
|
|
|
CLAIM FOR INTERCEPT OF TAX REFUND |
WARD, SHANTAL TEAIRRA |