| OLD line(s): 2
<xsd:schema targetNamespace="http://www.irs.gov/efile" xmlns="http://www.irs.gov/efile" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0"> | NEW line(s): 2
<xsd:schema xmlns="http://www.irs.gov/efile" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.irs.gov/efile" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0"> |
| OLD line(s): 6
<TaxYear>2012</TaxYear> | NEW line(s): 6
<TaxYear>2013</TaxYear> |
| OLD line(s): 11
| NEW line(s): 10
|
| OLD line(s): 13
| NEW line(s): 11
|
| OLD line(s): 17
| NEW line(s): 14
|
| OLD line(s): 39
| NEW line(s): 35
|
| OLD line(s): 45
| NEW line(s): 40
|
| OLD line(s): 47
| NEW line(s): 41
|
| OLD line(s): 49
| NEW line(s): 42
|
| OLD line(s): 52
<xsd:element name="Church170b1Ai" type="CheckboxType"> | NEW line(s): 45
<xsd:element name="ChurchInd" type="CheckboxType"> |
| OLD line(s): 60
| NEW line(s): 52
|
| OLD line(s): 62
<xsd:element name="School170b1Aii" type="CheckboxType"> | NEW line(s): 54
<xsd:element name="SchoolInd" type="CheckboxType"> |
| OLD line(s): 70
| NEW line(s): 61
|
| OLD line(s): 72
<xsd:element name="Hospital170b1Aiii" type="CheckboxType"> | NEW line(s): 63
<xsd:element name="HospitalInd" type="CheckboxType"> |
| OLD line(s): 80
| NEW line(s): 70
|
| OLD line(s): 83
<xsd:element name="MedicalResearchOrg170b1Aiii" type="CheckboxType"> | NEW line(s): 73
<xsd:element name="MedicalResearchOrganizationInd" type="CheckboxType"> |
| OLD line(s): 91
| NEW line(s): 80
|
| OLD line(s): 93
<xsd:element name="HospitalNameAndAddress" type="HospitalNameAndAddressType" maxOccurs="50"> | NEW line(s): 82
<xsd:element name="HospitalNameAndAddressGrp" type="HospitalNameAndAddressGrpType" maxOccurs="50"> |
| OLD line(s): 102
| NEW line(s): 90
|
| OLD line(s): 104
<xsd:element name="CollegeSupportOrg170b1Aiv" type="CheckboxType"> | NEW line(s): 92
<xsd:element name="CollegeOrganizationInd" type="CheckboxType"> |
| OLD line(s): 112
| NEW line(s): 99
|
| OLD line(s): 114
<xsd:element name="GovernmentalUnit170b1Av" type="CheckboxType"> | NEW line(s): 101
<xsd:element name="GovernmentalUnitInd" type="CheckboxType"> |
| OLD line(s): 122,123
| NEW line(s): 108
|
| OLD line(s): 125
<xsd:element name="PubliclySupportedOrg170b1Avi" type="CheckboxType"> | NEW line(s): 110
<xsd:element name="PublicOrganization170Ind" type="CheckboxType"> |
| OLD line(s): 133
| NEW line(s): 117
|
| OLD line(s): 135
<xsd:element name="CommunityTrust170b1Avi" type="CheckboxType"> | NEW line(s): 119
<xsd:element name="CommunityTrustInd" type="CheckboxType"> |
| OLD line(s): 143
| NEW line(s): 126
|
| OLD line(s): 145
<xsd:element name="PubliclySupportedOrg509a2" type="CheckboxType"> | NEW line(s): 128
<xsd:element name="PubliclySupportedOrg509a2Ind" type="CheckboxType"> |
| OLD line(s): 153
| NEW line(s): 135
|
| OLD line(s): 155
<xsd:element name="TestingForPublicSafety509a4" type="CheckboxType"> | NEW line(s): 137
<xsd:element name="TestPublicSafetyInd" type="CheckboxType"> |
| OLD line(s): 163
| NEW line(s): 144
|
| OLD line(s): 166
<xsd:element name="SupportingOrganization509a3" type="CheckboxType"> | NEW line(s): 147
<xsd:element name="SupportingOrganization509a3Ind" type="CheckboxType"> |
| OLD line(s): 174
| NEW line(s): 154
|
| OLD line(s): 176
<xsd:element name="SupportingOrg509a3Type1" type="CheckboxType"> | NEW line(s): 156
<xsd:element name="SupportingOrgType1Ind" type="CheckboxType"> |
| OLD line(s): 184,185
<xsd:element name="SupportingOrg509a3Type2" type="CheckboxType"> | NEW line(s): 164
<xsd:element name="SupportingOrgType2Ind" type="CheckboxType"> |
| OLD line(s): 193,194
<xsd:element name="SupportingOrg509a3Type3FuncInt" type="CheckboxType"> | NEW line(s): 172
<xsd:element name="SupportingOrgType3FuncIntInd" type="CheckboxType"> |
| OLD line(s): 202,203
<xsd:element name="SupportingOrg509a3Type3NonFunc" type="CheckboxType"> | NEW line(s): 180
<xsd:element name="SupportingOrgType3NonFuncInd" type="CheckboxType"> |
| OLD line(s): 212
| NEW line(s): 188
|
| OLD line(s): 215
| NEW line(s): 190
|
| OLD line(s): 217
<xsd:element name="CertificationCheckbox" type="CheckboxType" minOccurs="0"> | NEW line(s): 192
<xsd:element name="CertificationInd" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 225
| NEW line(s): 199
|
| OLD line(s): 227
<xsd:element name="WrittenIRSDetermination" type="CheckboxType" minOccurs="0"> | NEW line(s): 201
<xsd:element name="IRSWrittenDeterminationInd" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 235
| NEW line(s): 208
|
| OLD line(s): 238
<xsd:element name="ContribByControllingIndividual" type="BooleanType" minOccurs="0"> | NEW line(s): 211
<xsd:element name="ContributionControllerInd" type="BooleanType" minOccurs="0"> |
| OLD line(s): 246
| NEW line(s): 218
|
| OLD line(s): 248
<xsd:element name="ContributionByRelatedParty" type="BooleanType" minOccurs="0"> | NEW line(s): 220
<xsd:element name="ContributionFamilyInd" type="BooleanType" minOccurs="0"> |
| OLD line(s): 256
| NEW line(s): 227
|
| OLD line(s): 258
<xsd:element name="ContribBy35ControlledEntity" type="BooleanType" minOccurs="0"> | NEW line(s): 229
<xsd:element name="Contribution35ControlledInd" type="BooleanType" minOccurs="0"> |
| OLD line(s): 266
| NEW line(s): 236
|
| OLD line(s): 268
<xsd:element name="SupportedOrgInformation" type="SupportedOrgInformationType" minOccurs="0" maxOccurs="unbounded"> | NEW line(s): 238
<xsd:element name="SupportedOrgInformationGrp" type="SupportedOrgInformationGrpType" minOccurs="0" maxOccurs="unbounded"> |
| OLD line(s): 276
| NEW line(s): 245
|
| OLD line(s): 278
<xsd:element name="TotalNumberOfSupportedOrgs" type="IntegerNNType" minOccurs="0"> | NEW line(s): 247
<xsd:element name="SupportedOrganizationsTotalCnt" type="IntegerNNType" minOccurs="0"> |
| OLD line(s): 286
| NEW line(s): 254
|
| OLD line(s): 288
<xsd:element name="SumOfAmounts" type="USAmountType" minOccurs="0"> | NEW line(s): 256
<xsd:element name="SupportSumAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 296
| NEW line(s): 263
|
| OLD line(s): 300
| NEW line(s): 266
|
| OLD line(s): 302
<xsd:element name="GiftsGrantsContribReceived170" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 268
<xsd:element name="GiftsGrantsContriRcvd170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 310
| NEW line(s): 275
|
| OLD line(s): 312
<xsd:element name="TaxRevLeviedForOrgBenefit170" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 277
<xsd:element name="TaxRevLeviedOrgnztnlBnft170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 320
| NEW line(s): 284
|
| OLD line(s): 322
<xsd:element name="ValueSrvcFcltsFurnishedByGovt" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 286
<xsd:element name="GovtFurnSrvcFcltsVl170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 330
| NEW line(s): 293
|
| OLD line(s): 332
<xsd:element name="Total170" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 295
<xsd:element name="TotalCalendarYear170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 340
| NEW line(s): 302
|
| OLD line(s): 342
<xsd:element name="AmountsSubstContributorsTotal" type="USAmountType" minOccurs="0"> | NEW line(s): 304
<xsd:element name="SubstantialContributorsTotAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 350
| NEW line(s): 311
|
| OLD line(s): 352
<xsd:element name="PublicSupportTotal170" type="USAmountType" minOccurs="0"> | NEW line(s): 313
<xsd:element name="PublicSupportTotal170Amt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 360
| NEW line(s): 320
|
| OLD line(s): 363
| NEW line(s): 322
|
| OLD line(s): 365
<xsd:element name="GrossInvestmentIncome170" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 324
<xsd:element name="GrossInvestmentIncome170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 373
| NEW line(s): 331
|
| OLD line(s): 375
<xsd:element name="NetUBI" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 333
<xsd:element name="UnrelatedBusinessNetIncm170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 383
| NEW line(s): 340
|
| OLD line(s): 385
<xsd:element name="OtherIncome170" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 342
<xsd:element name="OtherIncome170Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 393
| NEW line(s): 349
|
| OLD line(s): 395
<xsd:element name="TotalSupport" type="USAmountType" minOccurs="0"> | NEW line(s): 351
<xsd:element name="TotalSupportAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 403
| NEW line(s): 358
|
| OLD line(s): 405
<xsd:element name="GrossReceiptsFromAdmissionsEtc" type="USAmountType" minOccurs="0"> | NEW line(s): 360
<xsd:element name="GrossReceiptsRltdActivitiesAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 413
| NEW line(s): 367
|
| OLD line(s): 415
<xsd:element name="First5Years170" type="CheckboxType" minOccurs="0"> | NEW line(s): 369
<xsd:element name="First5Years170Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 423
| NEW line(s): 376
|
| OLD line(s): 426
<xsd:element name="PublicSupportPertcentage170" type="RatioType" minOccurs="0"> | NEW line(s): 379
<xsd:element name="PublicSupportCY170Pct" type="RatioType" minOccurs="0"> |
| OLD line(s): 434
| NEW line(s): 386
|
| OLD line(s): 436
<xsd:element name="PublicSupportPertcentPriorYear" type="RatioType" minOccurs="0"> | NEW line(s): 388
<xsd:element name="PublicSupportPY170Pct" type="RatioType" minOccurs="0"> |
| OLD line(s): 444
| NEW line(s): 395
|
| OLD line(s): 446
<xsd:element name="ThirtyThreePercntTestsCY170" type="CheckboxType" minOccurs="0"> | NEW line(s): 397
<xsd:element name="ThirtyThrPctSuprtTestsCY170Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 454
| NEW line(s): 404
|
| OLD line(s): 456
<xsd:element name="ThirtyThreePercntTestsPY170" type="CheckboxType" minOccurs="0"> | NEW line(s): 406
<xsd:element name="ThirtyThrPctSuprtTestsPY170Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 464
| NEW line(s): 413
|
| OLD line(s): 466
<xsd:element name="TenPercentTestCurrentYear" type="CheckboxType" minOccurs="0"> | NEW line(s): 415
<xsd:element name="TenPctFactsCrcmstncsTestCYInd" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 474
| NEW line(s): 422
|
| OLD line(s): 476
<xsd:element name="TenPercentTestPriorYear" type="CheckboxType" minOccurs="0"> | NEW line(s): 424
<xsd:element name="TenPctFactsCrcmstncsTestPYInd" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 484
| NEW line(s): 431
|
| OLD line(s): 486
<xsd:element name="PrivateFoundation170" type="CheckboxType" minOccurs="0"> | NEW line(s): 433
<xsd:element name="PrivateFoundation170Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 494
| NEW line(s): 440
|
| OLD line(s): 496
| NEW line(s): 441
|
| OLD line(s): 499
<xsd:element name="GiftsGrantsContribReceived509" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 444
<xsd:element name="GiftsGrantsContrisRcvd509Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 507
| NEW line(s): 451
|
| OLD line(s): 509
<xsd:element name="GrossReceiptsFromAdmissions" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 453
<xsd:element name="GrossReceiptsAdmissionsGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 517
| NEW line(s): 460
|
| OLD line(s): 519
<xsd:element name="GrossReceiptsFromNonUBI" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 462
<xsd:element name="GrossReceiptsNonUnrltBusGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 527
| NEW line(s): 469
|
| OLD line(s): 529
<xsd:element name="TaxRevLeviedForOrgBenefit509" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 471
<xsd:element name="TaxRevLeviedOrgnztnlBnft509Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 537
| NEW line(s): 478
|
| OLD line(s): 539
<xsd:element name="ValueOfSvcsFcltsFurnishdByGovt" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 480
<xsd:element name="GovtFurnSrvcFcltsVl509Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 547
| NEW line(s): 487
|
| OLD line(s): 549
<xsd:element name="Total509" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 489
<xsd:element name="Total509Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 557
| NEW line(s): 496
|
| OLD line(s): 559
<xsd:element name="AmtsRecdFromDisqualPersons" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 498
<xsd:element name="AmountsRcvdDsqlfyPersonGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 567
| NEW line(s): 505
|
| OLD line(s): 569
<xsd:element name="AmtsFromSubstContributors" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 507
<xsd:element name="SubstantialContributorsAmtGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 577
| NEW line(s): 514
|
| OLD line(s): 579
<xsd:element name="SupportFromDQPsEtc" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 516
<xsd:element name="SubstAndDsqlfyPrsnsTotGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 587
| NEW line(s): 523
|
| OLD line(s): 589
<xsd:element name="PublicSupportTotal509" type="USAmountType" minOccurs="0"> | NEW line(s): 525
<xsd:element name="PublicSupportTotal509Amt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 597
| NEW line(s): 532
|
| OLD line(s): 600
| NEW line(s): 534
|
| OLD line(s): 602
<xsd:element name="GrossInvestmentIncome509" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 536
<xsd:element name="GrossInvestmentIncome509Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 610
| NEW line(s): 543
|
| OLD line(s): 612
<xsd:element name="Post1975UBTI" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 545
<xsd:element name="Post1975UBTIGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 620
| NEW line(s): 552
|
| OLD line(s): 622
<xsd:element name="InvestmentIncomeAndUBTI" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 554
<xsd:element name="InvestmentIncomeAndUBTIGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 630
| NEW line(s): 561
|
| OLD line(s): 632
<xsd:element name="NetIncomeFromOtherUBI" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 563
<xsd:element name="NetIncomeFromOtherUBIGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 640
| NEW line(s): 570
|
| OLD line(s): 642
<xsd:element name="OtherIncome509" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 572
<xsd:element name="OtherIncome509Grp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 650
| NEW line(s): 579
|
| OLD line(s): 652
<xsd:element name="TotalSupportTotal" type="Form990SchAPartIIGroup1Type" minOccurs="0"> | NEW line(s): 581
<xsd:element name="TotalSupportCalendarYearGrp" type="Form990SchAPartIIGroup1Type" minOccurs="0"> |
| OLD line(s): 660
| NEW line(s): 588
|
| OLD line(s): 662
<xsd:element name="First5Years509" type="CheckboxType" minOccurs="0"> | NEW line(s): 590
<xsd:element name="First5Years509Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 670
| NEW line(s): 597
|
| OLD line(s): 673
<xsd:element name="PublicSupportPercentage509" type="RatioType" minOccurs="0"> | NEW line(s): 600
<xsd:element name="PublicSupportCY509Pct" type="RatioType" minOccurs="0"> |
| OLD line(s): 681
| NEW line(s): 607
|
| OLD line(s): 683
<xsd:element name="PriorYearSupportPercentage" type="RatioType" minOccurs="0"> | NEW line(s): 609
<xsd:element name="PublicSupportPY509Pct" type="RatioType" minOccurs="0"> |
| OLD line(s): 691
| NEW line(s): 616
|
| OLD line(s): 694
<xsd:element name="InvestmentIncomePercentage" type="RatioType" minOccurs="0"> | NEW line(s): 619
<xsd:element name="InvestmentIncomeCYPct" type="RatioType" minOccurs="0"> |
| OLD line(s): 702
| NEW line(s): 626
|
| OLD line(s): 704
<xsd:element name="PriorYrInvestIncomePercentage" type="RatioType" minOccurs="0"> | NEW line(s): 628
<xsd:element name="InvestmentIncomePYPct" type="RatioType" minOccurs="0"> |
| OLD line(s): 712
| NEW line(s): 635
|
| OLD line(s): 714
<xsd:element name="ThirtyThreePercntTestsCY509" type="CheckboxType" minOccurs="0"> | NEW line(s): 637
<xsd:element name="ThirtyThrPctSuprtTestsCY509Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 722
| NEW line(s): 644
|
| OLD line(s): 724
<xsd:element name="ThirtyThreePercntTestsPY509" type="CheckboxType" minOccurs="0"> | NEW line(s): 646
<xsd:element name="ThirtyThrPctSuprtTestsPY509Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 732
| NEW line(s): 653
|
| OLD line(s): 734
<xsd:element name="PrivateFoundation509" type="CheckboxType" minOccurs="0"> | NEW line(s): 655
<xsd:element name="PrivateFoundation509Ind" type="CheckboxType" minOccurs="0"> |
| OLD line(s): 742
| NEW line(s): 662
|
| OLD line(s): 744
| NEW line(s): 663
|
| OLD line(s): 746
<xsd:element name="FactsAndCircumstancesTest" type="ExplanationType" minOccurs="0"> | NEW line(s): 665
<xsd:element name="FactsAndCircumstancesTestTxt" type="ExplanationType" minOccurs="0"> |
| OLD line(s): 754
| NEW line(s): 672
|
| OLD line(s): 756
<xsd:element name="GeneralExplanation" type="ExplanationType" minOccurs="0" maxOccurs="4"> | NEW line(s): 674
<xsd:element name="GeneralExplanationTxt" type="ExplanationType" minOccurs="0" maxOccurs="4"> |
| OLD line(s): 764
| NEW line(s): 681
|
| OLD line(s): 767
| NEW line(s): 683
|
| OLD line(s): 771
| NEW line(s): 686
|
| OLD line(s): 773
<xsd:complexType name="HospitalNameAndAddressType"> | NEW line(s): 688
<xsd:complexType name="HospitalNameAndAddressGrpType"> |
| OLD line(s): 776
<xsd:element name="Name" type="BusinessNameType" minOccurs="0"> | NEW line(s): 691
<xsd:element name="SupportedOrganizationName" type="BusinessNameType" minOccurs="0"> |
| OLD line(s): 784
| NEW line(s): 698
|
| OLD line(s): 786
<xsd:element name="City" type="CityType"> | NEW line(s): 700
<xsd:element name="CityNm" type="CityType"> |
| OLD line(s): 794
| NEW line(s): 707
|
| OLD line(s): 798
<xsd:element name="State" type="StateType"> | NEW line(s): 711
<xsd:element name="StateAbbreviationCd" type="StateType"> |
| OLD line(s): 806
| NEW line(s): 718
|
| OLD line(s): 808
<xsd:element name="Country" type="CountryType"> | NEW line(s): 720
<xsd:element name="CountryCd" type="CountryType"> |
| OLD line(s): 817
| NEW line(s): 728
|
| OLD line(s): 820
| NEW line(s): 730
|
| OLD line(s): 822
<xsd:complexType name="SupportedOrgInformationType"> | NEW line(s): 732
<xsd:complexType name="SupportedOrgInformationGrpType"> |
| OLD line(s): 825
<xsd:element name="Name" type="BusinessNameType"> | NEW line(s): 735
<xsd:element name="SupportedOrganizationName" type="BusinessNameType"> |
| OLD line(s): 833
| NEW line(s): 742
|
| OLD line(s): 843
| NEW line(s): 751
|
| OLD line(s): 845
<xsd:element name="TypeOfOrganization" type="ShortDescriptionType"> | NEW line(s): 753
<xsd:element name="OrganizationTypeDesc" type="ShortDescriptionType"> |
| OLD line(s): 853
| NEW line(s): 760
|
| OLD line(s): 855
<xsd:element name="ListedInGoverningDoc" type="BooleanType"> | NEW line(s): 762
<xsd:element name="GoverningDocumentListedInd" type="BooleanType"> |
| OLD line(s): 863
| NEW line(s): 769
|
| OLD line(s): 865
<xsd:element name="SupportedOrganizationNotified" type="BooleanType" minOccurs="0"> | NEW line(s): 771
<xsd:element name="SupportedOrgNotifiedInd" type="BooleanType" minOccurs="0"> |
| OLD line(s): 873
| NEW line(s): 778
|
| OLD line(s): 875
<xsd:element name="OrganizedInUS" type="BooleanType" minOccurs="0"> | NEW line(s): 780
<xsd:element name="USOrganizedInd" type="BooleanType" minOccurs="0"> |
| OLD line(s): 883
| NEW line(s): 787
|
| OLD line(s): 885
<xsd:element name="Amount" type="USAmountType"> | NEW line(s): 789
<xsd:element name="SupportAmt" type="USAmountType"> |
| OLD line(s): 893
| NEW line(s): 796
|
| OLD line(s): 896
| NEW line(s): 798
|
| OLD line(s): 901
<xsd:element name="CurrentTaxYearMinus4Years" type="USAmountType" minOccurs="0"> | NEW line(s): 803
<xsd:element name="CurrentTaxYearMinus4YearsAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 909
| NEW line(s): 810
|
| OLD line(s): 911
<xsd:element name="CurrentTaxYearMinus3Years" type="USAmountType" minOccurs="0"> | NEW line(s): 812
<xsd:element name="CurrentTaxYearMinus3YearsAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 919
| NEW line(s): 819
|
| OLD line(s): 921
<xsd:element name="CurrentTaxYearMinus2Years" type="USAmountType" minOccurs="0"> | NEW line(s): 821
<xsd:element name="CurrentTaxYearMinus2YearsAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 929
| NEW line(s): 828
|
| OLD line(s): 931
<xsd:element name="CurrentTaxYearMinus1Year" type="USAmountType" minOccurs="0"> | NEW line(s): 830
<xsd:element name="CurrentTaxYearMinus1YearAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 939
| NEW line(s): 837
|
| OLD line(s): 941
<xsd:element name="CurrentTaxYear" type="USAmountType" minOccurs="0"> | NEW line(s): 839
<xsd:element name="CurrentTaxYearAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 949
| NEW line(s): 846
|
| OLD line(s): 951
<xsd:element name="Total" type="USAmountType" minOccurs="0"> | NEW line(s): 848
<xsd:element name="TotalAmt" type="USAmountType" minOccurs="0"> |
| OLD line(s): 959
| NEW line(s): 855
|
| OLD line(s): 962
| NEW line(s): 857
|


A mathematical operation performed on a pair of numbers in order to derive a third number called a product. For positive integers, multiplication consists of adding a number (the multiplicand) to itself a specified number of times. Thus multiplying 6 by 3 means adding 6 to itself three times.
Drag the numbers to the above boxes see how multiplication works


{#==========================================
Docs : "HTTP Caching"
==========================================#}
Spincast supports many HTTP caching features, as described in the
HTTP 1.1 specification :
HTTP Caching
Finally, Spincast also provides a mechanism for Cache Busting.
Cache-Control
headers
Etag
headers
The Cache-Control
header (and the similar, but older, Expires
header) is used to
tell a client how much time (in seconds) it should use its cached copy of a resource
before asking the server for a fresh copy.
This Cache-Control
header can first be specified when you build a route (see
HTTP Caching route options), using the cache(...)
method.
router.GET("/test").cache(3600).handle(handler);
There are three options available when using this cache(...)
method :
public
(default) or private
. The private
option means an end client can cache the resource but not an intermediate proxy/CDN
(more information).
This cache(...)
method can also be used dynamically,
in a route handler, using the cacheHeaders()
add-on :
@Override public void myHandler(AppRequestContext context) { context.cacheHeaders().cache(3600); context.response().sendPlainText("This will be cached for 3600 seconds!"); }
When you do not explicitly set any caching options for a Static Resource
, some defaults are automatically used. Those
defaults are configurable using the SpincastConfig
class.
There are two variations for those Static Resources default caching configurations :
86400
seconds (1 day).
3600
seconds (1 hour).
When a resource can be generated, it often means that the resource may change more frequently. This is why
dynamic resources have their own default caching configuration.
When a Static/Dynamic Resource is served, a Last-Modified
header is also automatically
sent. This means that even when the client does ask for a fresh copy of a resource, it will often
receive a "304 - Not Modified"
response and will therefore again use its
cached copy, without unnecessary data being transferred over the network.
Finally, note that no default caching headers are sent for regular Routes. You have to explictly use
cache(...)
to send some. But if you use cache()
as is, without any parameter, then
default values will be used (still configurable using the SpincastConfig
class).
Even when no explicit caching headers are sent, some clients (browsers, proxies, etc.) may use a default caching strategy for the resources they download. For example, if you press the "back" button, many browsers will display a cached version of the previous page, without requesting the server for a fresh copy... Even if no caching headers were sent for that page!
If you want to tell the client that it should disable any kind of caching for a resource,
you can use the noCache(...)
method. This can be done when building a Route :
router.GET("/test").noCache().handle(handler);
Or can be used dynamically, in a Route Handler
:
@Override public void myHandler(AppRequestContext context) { context.cacheHeaders().noCache(); context.response().sendPlainText("This will never be cached!"); }
Finally, note that you can not use the noCache()
options on a Static Resource
since
this would defeat the notion of a "static" resource.
Cache busting is the process of adding a special token to the URL of a resource in a way that simply by changing this token you invalidate any cache a client may have.
For example, let's say that in a HTML page you reference a .css
file that you want
the client to cache (since it won't frequently change) :
<link rel="stylesheet" href="/public/css/main.css">
The associated Route may be :
router.file("/public/css/main.css").cache(86400).classpath("/css/main.css").handle();
As you now know, when this resource is served a Cache-Control
header will
be sent to the client so it caches it for 24 hours. And this is great! But what happens if you release
a new version of your application? You may then have changed "main.css"
and you want all clients
to use the new, fresh, version. How can you do that if many clients already have the old version in cache
and you specified them that they can use that cached version for 24 hours? This is where cache busting
become handy!
To enable cache busting for a particular resource, you add the "cacheBuster"
template
variable to its URL. This template variable is provided by Spincast, you simply need to add
it in your HTML pages. For example, if you use Pebble,
which is the default
Templating Engine
provided with Spincast, you need to use
"{% verbatim %}{{cacheBuster}}{% endverbatim %}"
as the cache buster token.
We recommend that you add this token right before the file name of the resource :
{% verbatim %}
<link rel="stylesheet" href="/public/css/{{cacheBuster}}main.css">{% endverbatim %}
When the HTML is rendered, the result will look something like this :
<link rel="stylesheet" href="/public/css/spincastcb_1469634250814_main.css">
When Spincast receives a request, it automatically removes any cache busters from the URL. So
"/public/css/spincastcb_1111111111111_main.css"
"/public/css/spincastcb_2222222222222_main.css"
"/public/css/main.css"
But (and that's the trick!) the client will consider both URLs as different, targeting different resources, so it won't use any cached version when a cache buster is changed!
By default, the cache busting code provided by Spincast will change every time the application is restarted. You can modify
this behavior and/or the format of the token by overriding the getCacheBusterCode()
and
removeCacheBusterCodes(...)
methods from
SpincastUtils.
Finally, note that the cache busting tokens are removed before the routing is done, so they don't affect it in any way.
The Etag
and Last modification date
headers are two ways of validating if the cached version
a client already has of a resource is still valid or not. We will call them "Freshness headers"
.
The client, when it wants to retrieve/modify/delete a resource it already has a copy of, sends a request
for that resource by passing the Etags
and/or Last modification date
it currently has for that
resource. The Server validates those values with the current information of the resource and decides if the
current resource should be retrieved/modified/deleted. Some variations using those headers are even used to
validate if a client can create a new resource.
Note that freshness headers management is not required on all endpoints. For example, an endpoint that would compute
the sum of two numbers has no use for cache headers or for freshness validation! But when a REST
endpoint deal with
a resource, by Creating, Retrieving, Updating or Deleting it, then freshness validation is a must
to respect the HTTP specification.
The most popular use for freshness headers is to return a 304 - Not Modified
response when a
client asks for a fresh copy of a resource but that resource has not changed. Doing so, the response
is very fast since no unnecessary data is actually transmitted over the network : the client simply continue to use its
cached copy.
This "304"
use case if often the only one managed by web frameworks. The reason is that it can
be automated, to some extent. A popular way of automating it is
to use an "after" filter to generate a hash from the body of a resource returned as the response to a
GET
request. This hash is used as an ETag
header and compared with any existing
If-None-Match
header sent by the client. If the ETag
matches, then the generated resource is
not sent, a "304 - Not Modified"
response is sent instead.
This approach may be attractive at first because it is very simple and doesn't require you to do anything except registering a filter. The problem is that this HTTP caching management is very, very, limited and only addresses one aspect of the caching mechanism described in the HTTP specification.
First, it only addresses GET
requests. Its only purpose is to return a 304 - Not Modified
response instead of the actual resource on a GET
request. But, freshness headers should be used
for a lot more than that. For example :
"If-Match"
(Etag) or an "If-Unmodified-Since"
(Last modification date) header, and the resource has changed, then the request must fail
and a 412 - Precondition Failed
response must be
returned. (specification)
"If-None-Match: *"
header is received on a PUT
request, the resource must not be created if any version of it already exists.
(specification)
Also, to hash the body of the resource to create an ETag
may not always be
appropriate. First, the resource must be generated for this hash to be computed.
But maybe you shouldn't have let the request access the resource in the first place! Also, maybe there is
a far better way to generate a unique ETag
for your resource than to hash its body, using one of its
field for example. Finally, what happens if you need to "stream" that resource?
If you need to flush the response more than once when
serving it? In that case, the "after" filter wouldn't be able to hash the body properly and
send it as an ETag
header.
All this to say that Etags
and Last modification date
may seem easy to manage
at first, but in fact, they require some work from you. If you simply want to manage the GET
use case where a 304 - Not Modified
response can be returned instead of the resource itself,
then creating your own "after" filter should be quite easy (we may even provide one in a future release). But if you want
your REST
endpoints to be more compliant with the HTTP specification, then keep reading
to learn how to use the cacheHeaders()
add-on and its validate()
method!
There are three methods on the cacheHeaders()
add-on made to deal with freshness headers in a
Route Handler
:
.etag(...)
.lastModified(...)
.validate(...)
The
first two are used to set the Etag
and Last modification date
headers
for the current version of the resource. For example :
// Set the ETag context.cacheHeaders().eTag(resourceEtag); // Set the Last modification date context.cacheHeaders().lastModified(resourceModificationDate);
But setting those freshness headers doesn't make sense if you do not validate them when they are sent
back by a client! This is what the .validate(...)
method is made for. It validates the current
ETag
and/or Last modification date
of the resource to the ones sent by the client.
Here's an example of what using this method looks like :
if(context.cacheHeaders().eTag(resourceEtag) .lastModified(resourceModificationDate) .validate(resource != null)) { return; }
We will look in details how to use the validate()
method, but the important thing to remember is
that if this method returns true
, then your route handler should return immediately,
without returning/modifying/creating
or deleting the associated resource. It also
means that the response to return to the client has already been set and should be returned as is : you
don't have to do anything more.
Note that, in general, you will use ETags
or Last modification dates
,
not both. Since ETags
are more generic (you can even use a modification date as an ETag
!), our following
example will only focus on ETags
. But using the validate(...)
method is the same, that you use
ETags
or Last modification dates
.
Let's first repeat that, as we previously said,
the Static Resources have their
Last modification date
automatically managed. The Server simply validates the modification
date of the resource's file on disk and use this information to decide if a new copy of the resource should be
returned or not. In other words, the validation pattern we are going to explain here only concerns regular Routes, where
Route Handlers
manage the target resources.
The freshness validation pattern looks like this, in a Route Handler
:
public void myRouteHandler(AppRequestContext context) { // 1. Gets the current resource, if any MyResource resource = getMyResource(); String resourceEtag = computeEtag(resource); // 2. Sets the current ETag and validates the freshness of the // headers sent by the client if(context.cacheHeaders().eTag(resourceEtag) .validate(resource != null)) { return; } // 3. Validation done! // Now the core of the handler can run : // it can create/return/update/delete the resource. // ... };
Explanation :
null
if it doesn't exist or if it has been deleted.
ETag
for the resource. The ETag
can be anything : it is specific to your application how to generate it.
Note that the ETag
can be null
if the resource doesn't exist!
cacheHeaders()
add-on, we set the ETag
of the current resource. This will add the appropriate headers to the response :
those headers will be sent, whatever the result of the validate(...)
method is.
validate(...)
method.
This method takes one parameter : a boolean indicating if the resource currently exists
or not. The method will validate the current ETag
and/or the Last modification date
with the ones received by the client. If any HTTP freshness rule is matched, some appropriate headers
are set in the response ("304 - Not Modified"
or "412 - Precondition Failed"
)
and true
is returned. If no freshness rule is matched, false
is returned.
validate(...)
method returns
true
, our Route Handler
should return immediately, without further processing!
validate(...)
method returns
false
, the main part of our Route Handler
can run, as usual.
As you can see, the validation pattern consists in comparing the ETag
and/or
Last modification date
of the actual resource to the headers
sent by the client. A lot of validations are done in that validate(...)
method,
we try to follow as much as possible the full HTTP specification.
Note that if the resource doesn't currently exist, you should not create it before calling
the validate(...)
method! You should instead pass false
to the validate(...)
method.
If the request is a PUT
asking to create the resource,
this creation can be done after the cache headers validation, and only if the validate(false)
method returns false
. In that case, the ETag
and/or Last modification date
will have to be added to the response by calling eTag(...)
and/or lastModified(...)
again :
public void createHandler(AppRequestContext context) { // Let's say the resource is "null" here. MyResource resource = getMyResource(); // The ETag will be "null" too. String resourceEtag = computeEtag(resource); if(context.cacheHeaders().eTag(resourceEtag) .validate(resource != null)) { return; } // The validation returned "false" so we can // create the resource! resource = createResourceUsingInforFromTheRequest(context); // We add the new ETag to the response. resourceEtag = computeEtag(resource); context.cacheHeaders().eTag(resourceEtag); }
If the resource doesn't exist and the request is a GET
, you can return
a 404 - Not Found
after the freshness validation. In fact, once the
validation is done, your handler can be processed as usual, as if there was no prior validation...
For example :
public void getHandler(AppRequestContext context) { MyResource resource = getMyResource(); String resourceEtag = computeEtag(resource); if(context.cacheHeaders().eTag(resourceEtag) .validate(resource != null)) { return; } if(resource == null) { throw new NotFoundException(); } return context.response().sendJson(resource); }
To conclude, you may now see that proper management of HTTP freshness headers
sadly can't be fully automated. A Filter
is simply not enough!
But, by using the
cacheHeaders()
add-on and its validate(...)
method, a
REST
endpoint can follow the HTTP specification and be very
performant. Remember that not all endpoints require that freshness validation, though! You can
start your application without any freshness validation at all and add it on endpoints
where it makes sense.


open terminal, run
python -m SimpleHTTPServer 3000
in the project directory, and navigate to
localhost:3000/example


OK so this goes out to all the professors that have such boring classes and are so in their own world when lecturing, that some students come in with their pillow and blanket and camp out! While it's hilarious, it's also an indicator for the current state of higher eduation. Below are some quick pointers for all you professors out there...
If you liked this page, vote here:


The Core Skills of my foundations journey was a pleasant surprise.
At the first moment you can ask yourself: What it means? I came here to learn how to code! It is true, but all the Core's content are helpful, actually crucial to me to learn how to code, and how to code well, especially because it is not only about code, but how you are going to do to solve it.
Yes, the first thing I have learned with DevAcademy and its core stuff is: the tech marked does not want developers to write codes, they want us to sort problems. So, I needed to learn how to do it and do it well. Actually, I am still learning but it is worth a lot.
The second important thing I have learnt was, I did know how to study. The Core brought me invaluable techniques that just saved my life forever. I need to assume it is still hard for me. It is challenging to have focus and discipline, but the results are so amazing that I definitely will use that for the rest of my life.
The third but not the last one was about my mindset to learn. How to have a growth mind and how important it is.
All information and techniques learnt are not so important to my learning time but also to my future as a developer. I can clearly see all the advantages to use then as professional, how to solve problems, how to work well and efficiently using timekeeping techniques and also to have a growth mindset and developer an emotional intelligence to deal with difficult tasks and colleagues.
This is an invaluable knowledge that is not taught in the college and it is something that usually we spend years to learn from the market. Definitely, the foundations core skills brought me knowledge that will make a difference in my life.


A macaron (/ˌmɑːkəˈrɒn/ mah-kə-rohn;[1] French pronunciation: [makaʁɔ̃]) is a French sweet meringue-based confection made with egg white, icing sugar, granulated sugar, almond powder or ground almond, and food colouring. The macaron is commonly filled with ganache, buttercream or jam filling sandwiched between two cookies. The name is derived from the Italian word macarone, maccarone or maccherone, the meringue.
The intricate confection is characterized by smooth, squared top, ruffled circumference (referred to as the "foot" or "pied"), and a flat base. It is mildly moist and easily melts in the mouth. Macarons can be found in a wide variety of flavors that range from the traditional (raspberry, chocolate) to the new (foie gras, matcha).[2] They are often said to be difficult to make.
The macaroon is often confused with the macaron; many have adopted the French spelling of macaron to distinguish the two items in the English language. However, this has caused confusion over the correct spelling. Some recipes exclude the use of macaroon to refer to this French confection while others think that they are synonymous.[3] In reality, the word macaroon is simply an Anglicisation of the French word macaron (compare balloon, from French ballon), so both pronunciations are technically correct depending on personal preference and context.[3] In a Slate article on the topic, Stanford Professor of linguistics and computer science, Dan Jurafsky, indicates that "macaron" (also, "macaron parisien", or "le macaron Gerbet") is the correct spelling for the confection.[4]
Source Wikipedia


This is a restaurant. It's cool.
Glossier chambray ennui, beard fashion axe small batch bicycle rights post-ironic raw denim. Craft beer chia bicycle rights air plant semiotics, portland salvia iceland narwhal meggings banh mi. Unicorn tote bag pop-up pinterest try-hard bicycle rights man braid vexillologist jianbing. Put a bird on it portland hella truffaut jean shorts, artisan tumblr la croix cred four loko taxidermy YOLO austin.


MiHome Smarthome settings
ioBroker IP:
ioBroker Port:
Default Gateway Key:
Double key interval (ms):
Gateway keys
IP Address
Key


Pellentesque et erat ac massa cursus porttitor eget sed magna.
This job was a great job for the pay and benefits when compared to waiting table and working fast food. I also preferred working for the vs other stores like . The biggest problem was unreasonable expectations from management. Even as one of there top employees you feel taken advantage of and over worked. Dealing with the customers was the other issue.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis varius hendrerit nisl id condimentum. Sed bibendum ultricies erat a vulputate. Curabitur id ultricies eros, at ultricies dui.
A Wal-Mart cashier is responsible for effectively executing and adhering to the “Basic Beliefs” of the founder, Sam Walton.
Vestibulum justo est, pharetra fermentum justo in, tincidunt mollis turpis. Duis imperdiet non justo euismod semper. Nullam laoreet est sit amet felis tristique laoreet. Duis interdum laoreet enim, at adipiscing velit viverra id.
Position: Manager, Accounter
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis varius hendrerit nisl id condimentum.
Vestibulum justo est, pharetra fermentum justo in, tincidunt mollis turpis. Duis imperdiet non justo euismod semper.
A Wal-Mart cashier is responsible for effectively executing and adhering to the “Basic Beliefs” of the founder.


PIG-DICE TIME!!
Rules for the game
Player one rolls the dice.
Player one can pass the dice to player two by clicking the hold button.
If player one rolls a "one" then he loses that round and player two takes over and vice versa.
The winner scores the highest addition when the dice is rolled.
enjoy the game
Player 1
Current Score:
Total Score:
Roll
Hold
Player 2
Current Score:
Total Score:
Roll
Hold
Restart


A hash function is a (mathematical) function which receives an input of arbitrary length and returns a function value (hash value) of a fixed length (usually 128 or 160 bits). The hash functions which are used in cryptography should be called one-way hash functions.
The hash function itself must be public, i.e. everyone should be able to (efficiently) calculate the hash value for a given input. Conversely, however, it must be (computationally) infeasible to find an input for a given value which possesses exactly the predetermined value as hash value (this is referred to as a one-way characteristic).
In cryptographic practice, generally hash functions must satisfy a second, more stringent requirement: it must be impossible to find two values which are mapped by the hash function onto the same hash value (collisions), since otherwise it would be possible to replace an already signed message after the event. Hash functions are especially used in connection with digital signatures. Here, for reasons of efficiency, the hash value of a message is signed instead of the message itself.
The hash value H = H(M) of an original message M, is used to check, if the received message M' has been changed.
Example: Some earlier computer magazines added row check sums to the printouts of source code examples. Using these check sums it was possible to recover fast typing errors of the printed source code, because only the row check numbers of the source code have to be checked to discover an error within a row (CDs and downloads didn't exist in these times).
For these checksum methods it is easy to find two different row messages R1, R2 with the same row check sum - meaning H(R1) = H(R2) but R1 != R2: So it is possible to compute a malicious modified source code, without the possibility to detect this modification only via checking the row check sums. We call two different rows with equal check sum a collision. In the notion of hash values we call this a collision if
M != M' and H(M) = H(M')
For cryptographic purposes we must consider the requirement that for the hashing method H and any message M it must be practically impossible to compute a collision. This means to compute a fake massage M' != M, with the characteristic H(M') = H(M).
In the example with the printed source code in earlier computer magazines simple checksum methods have been satisfying, because messages (lines) were not faked by will, but only accidentally mistyped.
CrypTool provides cryptographically strong hash methods via the Indiv. Procedures \ Hash menu. These hash methods compute for any document a hash value of constant length, independent whether if the input length is 1 byte or 1 Mbyte. The length of the output (hash value) is always between 16 bytes and 64 bytes (between 128 bit and 512 bit) long - depending on the hash method.


| DOSE: |
repeated |
IV |
Cocaine |
(powder / crystals) |
Since graduating from high school, I had constantly experimented with multiple substances--too many to list. Cocaine had always been a constant companion over the years because it was at once so cheap and so easy to obtain. At the age of twenty-three, I was returning to Austin, TX, after spending about a year at home, living clean, earning money, and generally getting my act together after a year of abuse and poverty.
A friend, Mr. M, who was fifty years old, offered me a place to stay upon my return. He had a one bedroom apartment, and he also worked from home. The conditions seemed perfect; I could take my time in finding the right job since I would stay rent-free. I knew that Mr. M still used cocaine himself, but I had thought that I would be able to avoid my own problems with the substance all together or, better yet, use it in a 'responsible' manner.
After returning from happy hour in the early afternoon the very first day that I had arrived in town, Mr. M offered me a small bag of coke. I accepted, but he told me that he wanted to make sure that I could keep his own usage a secret from our mutual friends. He told me that he didn't want others to know that he 'runs the drug.' By his lingo, I at first thought that he ran the drug for dealers at the bar while he was there, and I was fine with this sort of situation as long as there was no dealing from home. Just a moment later though, I understood what he meant by 'run.' He produced two syringes, and he handed one of them to me. I admitted that I had never tried the drug in this manner, and he offered to shoot me up for the first time.
The sensation is utterly deafening and overwhelming. I've heard it called the aluminum train, and this phrase is perhaps the catch-all that truly describes the power of the experience. It starts simply, like a thump to the chest. My heart slows for just a second, and the air is suddenly knocked from my lungs. The sounds around me quickly lessen and finally mute, and a metallic hiss screams so loudly that nothing else is possibly heard or understood. My skin grows cold and completely numb. Not a thought flows through my mind, and I feel as though I'm falling through the air at a million miles an hour.
This was truly the way the drug was meant to be experienced. Snorting or smoking come nowhere close to the power of this. Every inch of my body and every fold of my mind is completely enveloped. Even if it does only last just six or seven minutes, the rush is everlasting, and this is the very moment that true addiction begins.
It only took a few weeks for things to fall apart. Both encouraging each others' use, we spent all of our time each day locked inside our home, just waiting for the afternoon when we could return with a new batch to prep and shoot. It became ceremonious, and eventually, I would find myself shaking at the very thought of getting my hands on some.
After I was forced to return home because of the financial hardship that we had inflicted upon ourselves, my use stopped immediately. I no longer had access to the drug, and to this day, almost a full year later, I haven't even seen it since. But that wonderful ride to the edge of the cliff still haunts me, and my breath still grows short. My heart still pounds excitedly as I just imagine finding that time and place again. I am still addicted, mind and body.
Administering coke in this way opened a door that can never be closed. The gravity of the experience will never leave me. To this day, I still want and still plan to find my way back to this oh so empty space again, but I will always regret the moment when I decided to take the jump off of the cliff. There are certain things that man should never have to suffer, and this, by God, is undoubtedly one of them. My addiction has me, and I still hear the aluminum train rolling down its tracks, waiting for its stop when I climb aboard.
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.


Computer Programmer/Software Developer with more than 2 years in responsible for writing the programming code for user software requirements. expert in resolving business problems , advising on methods to improve company functionality. good Skills in Software Tester/ Test Analyst.
installing and configure computer hardware operating systems and applications monitoring and maintain computer systems and networks talk staff or clients through a series of actions, either face-to-face or over the phone, to help set up systems or resolve issues troubleshoot system and network problems, diagnosing and solving hardware or software faults replacing parts as required providing support, including procedural documentation and relevant reports.
following diagrams and written instructions to repair a fault or set up a system supporting the roll-out of new applications set up new users' accounts and profiles and deal with password issues responding within agreed time limits to call-outs work continuously on a task until completion (or referral to third parties, if appropriate) prioritising and manage many open cases at one time rapidly establish a good working relationship with customers and other professionals, such as software developers test and evaluate new technology conducting electrical safety checks on computer equipment.
GPA: 2.80
GPA: 96%
My Soulmate:cherry_blossom: INTERESTS • Excellent communication skills, both written and oral. • An excellent working knowledge of IT, media and all applications relating to communications. • Strong organizational skills & An efficient working manner. • The ability to manage a heavy workload and work well under pressure. • An excellent knowledge of the national and regional media. • The ability to work well as a team.


FreeCodeCamp Time Microservice Project
Enter dates as follows:
https://timestampmicroservice-likeclockwork.c9users.io/August 20, 2015
https://timestampmicroservice-likeclockwork.c9users.io/8-20-2015
https://timestampmicroservice-likeclockwork.c9users.io/1440028800
And get a timestamp object back as JSON.


I have been experimenting with BZP HCl recently to see if it would be a mild substitute for ecstasy or maybe even some sort of speed. I have never tried speed (caffeine) before but I think I have a good idea what it would
be like. I was a VERY hyper kid and in high school when people started doing drugs teachers would ask me If I had taken speed. Btw, I'm a sloppy writer so please excuse errors of any sort.
Anyway I have tried it about 7 times all in different doses, oral and smoked. It's a white powder that clumps into nuggets easily if allowed contact with moisture.
I'm not going to go into any actual trip reports because my activities while high were very mundane and the drug didn't change them much. I watched a few movies played computer games etc...
THE BREAK DOWN:
* Time. coming up -> 1.5 hours, peak -> 2.5 hours, come down -> 3+
* Oral Doses: 20mg, 60mg, 100mg, 200mg, 300mg. This is interesting. After I got past about 100mg I couldn't tell the difference. hmmmmmm.
* Smoking: I smoked the stuff a few times in probably around 7mg doses. It tasted poor but not bad. It hit me about 2 mins after smoking. I got a mild rush which was nice but taking it orally lasted longer and heating
chemicals can change their make up and I'm not sure I want to mess with that.
* Snorting: I never snorted it because the one dab I put in my nose burned. I would imagine snorting to be VERY painful.
* Pros: Mild-medium euphoria, 'warm fuzzy' body high resembling a low dose of X (~30mg+). Increased energy and need to talk/relate/move etc... I also found rubbing things and playing with objects like hair to be fun and feel quite good. The one way it was most like x was the feelings of being open, connected, love. This aspect was actually pretty damn close to x (75mg+). But then again emotional openness is often very psychosomatic. So that means when you take it expect a love filled emotional trip and it will happen.
* Cons: Fast heart beat (90-120Bpm), VERY sweaty arm pits. I would sweat like a hog for 3 some hours, Mild body temperature increase. Mild nausea for about 10-15 mins about 40 mins after dosing, bad cotton mouth, dilated pupils.
* Neutral: Loss of appetite, hard to sleep, difficulty climaxing.
* Addiction: This stuff is addicting. It's very mild, tolerable, cheap and makes you feel that much better. That combo makes addiction very possible.
* Interactions: I found BZPto mix VERY well with weed. The body high was increased from about 30mg of X to maybe 50mg+. The bad part was that the cotton mouth became unbearable. BZP also mixed well with booze and GHB. I didn't feel that much drunker but the speed like effects went up, which was odd. I plan to mix it with LSD and similars in the future.
THE BOTTOM LINE: BZP seems to be a mild stimulant with effects similar to 30mg of X or a very low dose of amphetamine. A good relation we can make to speed is caffeine. 100mg of BZP had the speedy effects of ~3 cups of coffee. BZP would mix good with x if you DON'T dance on it but I still don't think it would be a good replacement, it's just not powerful enough.
As for replacing some sort of speed I believe it could replace a low dose of amphetamine (and I again I have never done it) but it could never replace meth or anything of that caliber. If your looking for speed look some place else! I'm sure BZP would be great for recovering speed, x etc.. addicts. All in all I like it as a mild drug, for mild activites. but decide for yourself!!
The question I'm left with for myself, is BZP too mild to be good alone? It was DEFINITELY good to mix other drugs with but alone was just not enough to sustain a drug induced night. I'm kind of glad it isn't too strong though. If it was any stronger then it is it would be too addicting to be even worth experimenting with.
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.


THE PURPLE ROSE OF CAIRO (1985) A Film Review by Ted Prigge Copyright 1998 Ted Prigge
Writer/Director: Woody Allen Starring: Mia Farrow, Jeff Daniels, Danny Aiello, Irving Metzman, Stephanie Farrow, Edward Herrman, John Wood, Deborah Rush, Van Johnson, Zoe Caldwell, Eugene J. Anthony, Ebb Miller, Karen Akers, Annie Joe Edwards, Milo O'Shea, Peter McRobbie, Alexander H. Cohen, Michael Tucker, Glenne Hedley, Diane Wiest
I was once engaed in a lunch-time argument back in high school over the need for films. My one friend deemed that they're not necessary at all, and that taking them away would cause no real drift in the morale of the nation. I disagreed vehemently: films are, above all, entertainment, and can enlighten people's lives, open their eyes, and cheer up the morale of the nation. And that's what Woody Allen's "Purple Rose of Cairo" is all about: films are necessary not only as an art form, but as a way to change lives.
The plot of the film, though, sounds gimmicky (and also very reminiscent of "The Last Action Hero"): a character from the movies comes down from the screen to be in real life with a woman whom he wants to meet. But that's what's cool about Woody Allen: he takes these kinds of ideas, and goes off on philosophical rants with them, but never loses sight of the plot or makes them too preachy. This is exactly how the film is played out, and is in retrospect a classic of cinema.
"The Purple Rose of Cairo" is the name of the movie in the film which our protagonist, the weak Cecilia (Mia Farrow), goes to see to escape from the unhappiness of her life. It's the Great Depression, and she has a horrible waitress job which she's no good at, a louse for a husband (Danny Aiello - who else could have played this role?) who takes her pay to gamble and drink, and is just generally miserable. Every week, the local Jersey theatre plays a new Hollywood film, and she goes every week, sometimes numerous times.
In the week of the film, the eponomys film is playing, and Cecilia shows up. It's some really hokey yet escapist film dealing with aristocrats who journey to Egypt and meet a happy-go-lucky explorer named Tom Baxter (Jeff Daniels), and take them home with them for a "madcap Manhattan weekend." After numerous airings of it, and after some more life complications, Tom begins stumbling over his lines, and looks out into the audience and begins talking to Cecilia, who's the most startled in the theatre. He walks down off the screen, takes her out of the theatre, and declares he'll never go back.
The rest of the film deals with her relationship with him, and how they fall in love like in a Hollywood film, but with the major setbacks of reality. But while they're dancing and talking around town, the characters in the movie are stuck on screen since they can't turn the projector off or Tom will be stuck in the real world forever. Soon, Hollywood is notified, and the producers, and the actor who plays Tom in the movie, Gil Shepard (also Jeff Daniels - duh!), fly out to Jersey to stop him.
As the movie goes on, more and more complications emerge. Cecilia's husband learns of her new romance, and begins making brutal attempts to reclaim his prize from the fictional Tom. And Gil stumbles into Cecilia by accident, and soon, he's falling in love with her, making her chose between the fictitious Tom, and the real Gil, a rising star. She exclaims at one point: "Yesterday, no one loved me; now two people love me!"
What's magical about "The Purple Rose of Cairo" is how balanced it is in every way. Woody deftly creates multilpe themes and thoughts on film and its relation to reality without ever harming the story, but also makes the two work hand-in-hand. By having a reason for Tom to walk off the screen, he creates a fantastically leveled fable on life, and how film can truly affect it.
Woody's also very responsible about it. If taken out of hand, film can cause people to blur reality with the fictitious, which is made notable through Cecilia's relationships with Tom and Gil. Through this conflict, Woody shows that people often want to be just like the people in the movie, while at the same time, the characters in the movie want to be people in reality.
People often rate Woody's films as how funny they are. "The Purple Rose of Cairo" is no exception, with lots of hysterical jokes here and there, and brilliantly funny scenes. There are plenty of fish-out-of-water jokes, but they never feel forced, and in fact, seem quite inspired, even by today's standards. And any of the scenes involving the characters stuck on the screen, bickering and trying to pass the days away are funny as hell. But all of this has a kind of deeper warmth to it, allowing some drama to flow effortlessly through the narrative, but never seem like melodrama.
The acting's also excellent, especially by Farrow, who gives what is probably her best performance in a Woody Allen film. She posesses true likability, and plays her character as weak yet somehow optimistic when watching a movie. There's a shot where she's going to see the movie for the first time where she looks so ecstatic that she looks like she's going to burst. Jeff Daniels has a lot of energy in his roles, giving one of his best performances (special note: the split-screen effect looks flawless). Danny Aiello adds some human qualities to his role as a no-good husband. And we even get some cameos from Milo O'Shea (remember Durand Durand from "Barbarella?") as a priest in the movie, and Diane Wiest as (get this) a hooker (showing that Woody sure has a knack for writing hooker roles).
The final shot is one of the great Woody Allen moments: a shot of Mia gazing upon the movie screen where Fred Aistaire is singing "I'm in Heaven," and gradually, a small smile grows on Cecilia's face. For this moment, no matter what the trouble is in the world, she's in heaven like the characters in the movie. This is the power of movies: to cause people to relax and escape from the horrors of reality, if only for a short time. This film is a masterpiece.
MY RATING (out of 4): ****
Homepage at: http://www.geocities.com/Hollywood/Hills/8335/
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


WATCH: #KFCProposal couple has a ball at the Soweto derby
by Azarrah KarrimThe KFC couple, South Africa's favourite newly-weds-to-be, has been spotted enjoying their weekend at the Soweto derby on Saturday.
Bhut' Hector and his soon-to-be wife, Nonhlanhla, were captured dancing together while watching Kaizer Chiefs and Orlando Pirates at the FNB Stadium in Johannesburg.
The couple, who are Chiefs supporters, had more reason to smile as their team edged out their rivals 3-2.
The couple found a place in the hearts of many South Africans when a video of Bhut' Hector taking a knee to propose to Nonhlanhla in a KFC in the Vaal went viral.
KFC called on South Africans to help them find the couple.
Soon after, companies pledged their services to the couple, including Kulula, Standard Bank, Audi, Coca-Cola and Woolworths, to name a few.
Celebrity personalities Zakes Bantwini, DJ Fresh and Donald and DJ PH offered their services for the much-anticipated wedding.
According to the Sowetan, the couple has thanked South Africans for their love and support but said they would like their privacy for the time-being.


|
Attribute
|
Description
|
Type
|
Requirement
|
|
classname
|
Class name for a user-supplied project writer. Use the "type" attribute to specify built-in project writer implementations.
|
String
|
Optional
|
|
description
|
|
String
|
|
failonerror
|
Sets whether a failure to write the project file should cause the task to fail. Default is true.
|
boolean
|
|
if
|
Sets the property name for the 'if' condition. The configuration will be ignored unless the property is defined. The value of the property is insignificant, but values that would imply misinterpretation ("false", "no") will throw an exception when evaluated.
|
String
|
|
name
|
Set name.
|
String
|
|
outfile
|
Sets the name for the generated project file.
|
File
|
|
overwrite
|
Sets whether an existing project file should be overwritten, default is true. If false and the project file exists, the value of failonerror will determine if the task fails.
|
boolean
|
|
refid
|
|
Reference
|
|
type
|
Set project type. Supported project formats | cbuilderx | Borland C++BuilderX | | msvc5 | Microsoft Visual C++ 97 | | msvc6 | Microsoft Visual C++ 6 | | msvc7 | Microsoft Visual C++.NET | | msvc71 | Microsoft Visual C++.NET 2003 | | msvc8 | Microsoft Visual C++ 2005 | | xcode | Apple Xcode |
|
"cbuilderx", "msvc5", "msvc6", "msvc7", "msvc71", "msvc8", "xcode"
|
|
unless
|
Set the property name for the 'unless' condition. If named property is set, the configuration will be ignored. The value of the property is insignificant, but values that would imply misinterpretation ("false", "no") of the behavior will throw an exception when evaluated.
|
String
|


{% extends "base_sidenav.html" %} {% load compress %} {% block css %}{{ block.super }} {% include "d3_css.html" %} {% endblock %} {% block header %}
(-2000 indicates that the load time was not measured)


Your message titled "{{this_contact.title}}" has been received. You'll receive a reply shortly on your email.


CardPage
class CardPage extends FormPage (View source)
CardPage class
Properties
| protected string | $head | from Page | |
| protected string | $title | from Page | |
| protected string | $access_permission | from Page | |
| protected array | $tabs | from Page | |
| protected array | $main_subtitle | from Page | |
| protected string | $tabs_picture | from Page | |
| protected string | $tabs_title | from Page | |
| protected string | $active_tab | from Page | |
| protected boolean | $close_form | from Page | |
| protected boolean | $close_table | from Page | |
| protected boolean | $add_fiche_end | from Page | |
| protected string | $rights_class | from Page | |
| protected string | $modulepart | from Page | |
| protected array | $assets | from Page | |
| object | $form | from FormPage | |
| protected string | $body | from FormPage | |
| protected array | $fields | from FormPage | |
| protected string | $edit_permission | ||
| protected string | $delete_permission | ||
| protected boolean | $close_buttons_div | ||
| protected boolean | $show_documents | ||
| protected string | $const_name_prefix | ||
| protected string | $sub_permission | ||
| protected string | $mail_subject | ||
| protected string | $mail_template | ||
| protected array | $mail_substitutions | ||
| protected boolean | $enable_mail_delivery_receipt | ||
| protected object | $extrafields |
Methods
Constructor
Add a subtitle
Opens a new html table
Include a template into the page.
Generate page beginning
Generate page end
Check specified field
Show a confirmation message
Return if the current user can edit the page or not
Return if the current user can delete the object or not
Set mail subject
Set mail template
Enables mail delivery receipt
Set mail substitutions
Open buttons div (if not already opened)
Close buttons div (if opened)
Add a button to the page
Add a confirmation button to the page
Add a list button to the page
Add save as button to the page
Show a table field
Show reference/Ref. field
Show extra fields
Update extra fields
Show banner
Edit a field
Add a table field with a text input
Add a table field with a text area
Add a table field with a number input
Add a table field with a date picker
Add a table field with a list
Add a table field with a radio input(s)
Add a table field with a checkbox input(s)
Add a table field with a color picker
Print related objects block.
Print documents block
Print mail form
Details
at line 87
__construct($page_title, $access_perm = '', $edit_perm = '', $delete_perm = '', $show_documents = false, $enable_save_as = false, $const_name_prefix = '', $sub_permission = '')
Constructor
$this
setTitle($page_title)
Set page title.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
setMainSubtitle($title, $picture = 'title_generic.png')
Set page main subtitle.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
loadLangs($lang_files_array, $from_module = false)
Load an array of language files
$this
appendToHead($content)
Append content to page head.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
addJsFile($js_file)
Add JS file to page head.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
addJsFiles($js_files_array)
Add an array of JS files.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
addCssFile($css_file)
Add CSS file to page head.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
addCssFiles($css_files_array)
Add an array of CSS files.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
addTab($title, $url, $is_active = false, $position = -1)
Add a tab to the page.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
setTabsPicture($picture)
Set tabs picture.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
setTabsTitle($title)
Set tabs title.
Note: this function should be called before $page->begin() function, otherwise it will not work as expected.
$this
addSubTitle($title, $picture = 'title_generic.png', $morehtmlright = '')
Add a subtitle
$this
openForm($action = 'create', $enctype = '')
Open a form only if not already opened
$this
openTable($header_columns = array(), $attr = 'class="noborder allwidth"', $print_fiche_head = false, $summary = '')
Opens a new html table
$this
showTemplate($template_path, $path_is_absolute = false, $use_require_once = false, $template_params = array())
Include a template into the page.
Note: the template should be inside module tpl folder when $path_is_absolute parameter equal false.
at line 791
$this
begin()
Generate page beginning
redirect($url)
Redirect to a url (alias for dolibase_redirect function).
Note: this function should be called before any output, so before $page->begin() function.
at line 806
end($object = null)
Generate page end
boolean|int
checkField($field_name, $field_trans = '', $field_validation_rules = '', $return_err_number = false)
Check specified field
$this
askForConfirmation($url, $title, $question, $action, $question_param = '', $dialog_id_suffix = '')
Show a confirmation message
at line 127
boolean
canEdit()
Return if the current user can edit the page or not
at line 137
boolean
canDelete()
Return if the current user can delete the object or not
at line 148
$this
setMailSubject($mail_subject)
Set mail subject
at line 161
$this
setMailTemplate($mail_template)
Set mail template
at line 173
$this
enableMailDeliveryReceipt()
Enables mail delivery receipt
at line 186
$this
setMailSubstitutions($mail_substitutions_array)
Set mail substitutions
at line 197
protected
openButtonsDiv()
Open buttons div (if not already opened)
at line 211
protected
closeButtonsDiv()
Close buttons div (if opened)
at line 229
$this
addButton($name, $href = '#', $target = '_self', $class = 'butAction', $close_parent_div = false)
Add a button to the page
at line 255
$this
addConfirmButton($name, $id, $href = '#', $target = '_self', $class = 'butAction', $close_parent_div = false)
Add a confirmation button to the page
at line 286
$this
addListButton($name, $buttons = array(), $class = 'butAction', $close_parent_div = false)
Add a list button to the page
at line 329
$this
addSaveAsButton($close_parent_div = false)
Add save as button to the page
at line 351
$this
showField($field_name, $field_content, $is_editable = false, $edit_link = '', $attr = '')
Show a table field
at line 376
$this
showRefField($field_name, $object, $list_link = '')
Show reference/Ref. field
at line 394
$this
showExtraFields($object)
Show extra fields
at line 420
int
updateExtraFields($object)
Update extra fields
at line 450
$this
showBanner($object, $list_link = '', $morehtmlleft = '')
Show banner
at line 471
$this
editField($field_name, $field_content, $action_name)
Edit a field
at line 502
$this
editTextField($field_name, $input_name, $input_value = '', $input_size = 20, $action_prefix = 'set_')
Add a table field with a text input
at line 522
$this
editTextAreaField($field_name, $text_area_name, $text_area_value = '', $toolbarname = 'dolibarr_details', $height = 100, $action_prefix = 'set_')
Add a table field with a text area
at line 542
$this
editNumberField($field_name, $input_name, $input_value = '', $min, $max = 100, $action_prefix = 'set_')
Add a table field with a number input
at line 562
$this
editDateField($field_name, $input_name, $input_value = '', $action_prefix = 'set_date_')
Add a table field with a date picker
at line 582
$this
editListField($field_name, $list_name, $list_choices, $selected_choice = '', $show_empty, $action_prefix = 'set_')
Add a table field with a list
at line 601
$this
editRadioListField($field_name, $radio_name, $radio_list, $selected = '', $action_prefix = 'set_')
Add a table field with a radio input(s)
at line 620
$this
editCheckListField($field_name, $check_name, $check_list, $selected = '', $action_prefix = 'set_')
Add a table field with a checkbox input(s)
at line 638
$this
editColorField($field_name, $input_name, $input_value = '', $action_prefix = 'set_')
Add a table field with a color picker
at line 653
protected
printRelatedObjects($object)
Print related objects block.
Note: To enable the linking feature, you must define a constant in each module as 'your_module_right_class_in_capital_letters'.'_ENABLE_EXPANDED_LINKS'
at line 693
protected
printDocuments($object)
Print documents block
at line 731
protected
printMailForm($object)
Print mail form


{% extends "withoutnav_template.html" %} {% block per_page_title %} Using GOV.UK Notify {% endblock %} {% block maincolumn_content %}
All new accounts on Notify start off in trial mode.
This means:
When you’re ready we can {% if current_service %} remove these restrictions. {% else %} remove these restrictions. {% endif %}
If a message fails because the inbox or phone ‘isn’t accepting messages right now’ then it’s up to you to decide if you want to send the message again or not.
Notify attempts to send messages for up to 72 hours before it returns that status.
If your user has provided you with multiple contact channels, you should send messages to the channel they’ve chosen as their preference. However there are some scenarios where you might want to send messages to more than one channel:
If you’re using the Notify API these scenarios could be automated.
Replies to emails that you’ve sent will go directly to the reply-to address that you have set up for your service.
If you’re set up to receive text messages then your users can reply to messages you’ve sent, or can start an interaction by sending you a text message.
Receiving inbound text messages can allow your service users to:
You’ve then got the option to automate the processing of the messages you receive, or to view them in Notify.
If you automate the processing of text messages you receive, then you should have a manual process in place to deal with messages that can’t be automatically processed.
If you’d like your service to receive text messages, then let us know.
Our delivery states are:
All messages start in the ‘Sending’ state.
This means that we have accepted the message. It’s waiting in a queue to be sent to our email or text message delivery partners.
This means the message is in the person’s email inbox or on their phone.
We can’t tell you if they’ve read it – to do so would require invasive and unreliable tracking techniques.
This means the text message has been sent to a valid international phone number, but delivery receipts aren’t provided by mobile networks in that country.
You’re still billed for text messages to non-existent phone numbers.
You need to remove these email addresses or phone numbers from your database.
This can happen for a number of reasons, eg the user’s inbox was full.
You can choose to retry these messages later or not.
This means the user’s phone was full or hasn’t been switched on in the last 72 hours.
You’re still billed for these messages.
You can choose to retry these messages later or not.
This means there is a problem with the connection between Notify and our email or text message delivery partners.
Messages still being retried are marked as ’Sending’. We mark messages as ‘Technical failure’ once we’ve given up.
You won’t be billed for these messages.
You need to retry these messages yourself later.