{
    "mode": "perldoc",
    "parameter": "Net::Jabber::Dialback::Verify",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/perldoc/Net%3A%3AJabber%3A%3ADialback%3A%3AVerify/json",
    "generated": "2026-07-05T13:53:21Z",
    "synopsis": "Net::Jabber::Dialback::Verify is a companion to the Net::Jabber::Dialback\nmodule.  It provides the user a simple interface to set and retrieve all\nparts of a Jabber Dialback Verify.",
    "sections": {
        "NAME": {
            "content": "Net::Jabber::Dialback::Verify - Jabber Dialback Verify Module\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "Net::Jabber::Dialback::Verify is a companion to the Net::Jabber::Dialback\nmodule.  It provides the user a simple interface to set and retrieve all\nparts of a Jabber Dialback Verify.\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "To initialize the Verify with a Jabber <db:*/> you must pass it\nthe XML::Stream hash.  For example:\n\nmy $dialback = new Net::Jabber::Dialback::Verify(%hash);\n\nThere has been a change from the old way of handling the callbacks.\nYou no longer have to do the above yourself, a NJ::Dialback::Verify\nobject is passed to the callback function for the message.  Also,\nthe first argument to the callback functions is the session ID from\nXML::Streams.  There are some cases where you might want this\ninformation, like if you created a Client that connects to two servers\nat once, or for writing a mini server.\n\nuse Net::Jabber qw(Server);\n\nsub dialbackVerify {\nmy ($sid,$Verify) = @;\n.\n.\n.\n}\n\nYou now have access to all of the retrieval functions available.\n\nTo create a new dialback to send to the server:\n\nuse Net::Jabber qw(Server);\n\n$Verify = new Net::Jabber::Dialback::Verify();\n\nNow you can call the creation functions below to populate the tag before\nsending it.\n\nFor more information about the array format being passed to the CallBack\nplease read the Net::Jabber::Client documentation.\n",
            "subsections": [
                {
                    "name": "Retrieval functions",
                    "content": "$to         = $Verify->GetTo();\n$from       = $Verify->GetFrom();\n$type       = $Verify->GetType();\n$id         = $Verify->GetID();\n$data       = $Verify->GetData();\n\n$str        = $Verify->GetXML();\n@dialback   = $Verify->GetTree();\n"
                },
                {
                    "name": "Creation functions",
                    "content": "$Verify->SetVerify(from=>\"jabber.org\",\nto=>\"jabber.com\",\nid=>id,\ndata=>key);\n$Verify->SetTo(\"jabber.org\");\n$Verify->SetFrom(\"jabber.com\");\n$Verify->SetType(\"valid\");\n$Verify->SetID(id);\n$Verify->SetData(key);\n"
                },
                {
                    "name": "Test functions",
                    "content": "$test = $Verify->DefinedTo();\n$test = $Verify->DefinedFrom();\n$test = $Verify->DefinedType();\n$test = $Verify->DefinedID();\n"
                }
            ]
        },
        "METHODS": {
            "content": "",
            "subsections": [
                {
                    "name": "Retrieval functions",
                    "content": "GetTo() -  returns a string with server that the <db:verify/> is being\nsent to.\n\nGetFrom() -  returns a string with server that the <db:verify/> is being\nsent from.\n\nGetType() - returns a string with the type <db:verify/> this is.\n\nGetID() - returns a string with the id <db:verify/> this is.\n\nGetData() - returns a string with the cdata of the <db:verify/>.\n\nGetXML() - returns the XML string that represents the <db:verify/>.\nThis is used by the Send() function in Server.pm to send\nthis object as a Jabber Dialback Verify.\n\nGetTree() - returns an array that contains the <db:verify/> tag\nin XML::Parser::Tree format.\n"
                },
                {
                    "name": "Creation functions",
                    "content": "SetVerify(to=>string,   - set multiple fields in the <db:verify/>\nfrom=>string,   at one time.  This is a cumulative\ntype=>string,   and over writing action.  If you set\nid=>string,     the \"from\" attribute twice, the second\ndata=>string)   setting is what is used.  If you set\nthe type, and then set the data\nthen both will be in the <db:verify/>\ntag.  For valid settings read the\nspecific Set functions below.\n\nSetTo(string) - sets the to attribute.\n\nSetFrom(string) - sets the from attribute.\n\nSetType(string) - sets the type attribute.  Valid settings are:\n\nvalid\ninvalid\n\nSetID(string) - sets the id attribute.\n\nSetData(string) - sets the cdata of the <db:verify/>.\n"
                },
                {
                    "name": "Test functions",
                    "content": "DefinedTo() - returns 1 if the to attribute is defined in the\n<db:verify/>, 0 otherwise.\n\nDefinedFrom() - returns 1 if the from attribute is defined in the\n<db:verify/>, 0 otherwise.\n\nDefinedType() - returns 1 if the type attribute is defined in the\n<db:verify/>, 0 otherwise.\n\nDefinedID() - returns 1 if the id attribute is defined in the\n<db:verify/>, 0 otherwise.\n"
                }
            ]
        },
        "AUTHOR": {
            "content": "By Ryan Eatmon in May of 2001 for http://jabber.org..\n",
            "subsections": []
        },
        "COPYRIGHT": {
            "content": "This module is free software; you can redistribute it and/or modify it under the same terms as\nPerl itself.\n",
            "subsections": []
        }
    },
    "summary": "Net::Jabber::Dialback::Verify - Jabber Dialback Verify Module",
    "flags": [],
    "examples": [],
    "see_also": []
}