Net::E...Contact(3pm)
π Net::EPP::Frame::Command::Delete::Contact(3pm) π
okay bestie, sit DOWN because we're about to talk about Net::EPP::Frame::Command::Delete::Contact β and yeah that name is a whole mouthful, it's giving "my parents named me after the entire family tree", but I promise she's worth it π«Ά
So basically: this is one specific flavor of Net::EPP::Frame::Command::Delete, and the flavor is contact objects. Deleting a contact. That's the whole vibe. No cap β¨
β¨ NAME β¨
Net::EPP::Frame::Command::Delete::Contact β an instance of Net::EPP::Frame::Command::Delete for contact objects. π
πΈ SYNOPSIS πΈ
here's the whole serve, look:
use Net::EPP::Frame::Command::Delete::Contact;
use strict;
my $delete = Net::EPP::Frame::Command::Delete::Contact->new;
$delete->setContact('contact-id');
print $delete->toString(1);
and like⦠this results in an XML document like this:
<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
epp-1.0.xsd">
<command>
<delete>
<contact:delete
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
contact-1.0.xsd">
<contact:name>contact-idE<lt>/contact:name>
</contact:delete>
</delete>
<clTRID>0cf1b8f7e14547d26f03b7641660c641d9e79f45</clTRIDE<gt>
</command>
</epp>
look at her go π iconic behaviour, honestly. yes the <clTRID> is random-looking, that's literally the point, she's built different π₯
π OBJECT HIERARCHY π
the family tree, and yes she comes from a long line of distinguished ancestors:
L<XML::LibXML::Node>
+----L<XML::LibXML::Document>
+----L<Net::EPP::Frame>
+----L<Net::EPP::Frame::Command>
+----L<Net::EPP::Frame::Command::Delete>
+----L<Net::EPP::Frame::Command::Delete::Contact>
she's the youngest, she's the baby of the family, and she eats every single time π
π¦ METHODS π¦
$frame->setContact($domain_name);β this specifies the contact object to be deleted. that's it, that's the method. one job, does it flawlessly, main character energy π
ngl bestie, $domain_name is literally what the original calls it, even though we're deleting a contact and not a domain. i don't make the rules, i just deliver them with glitter. π
π SEE ALSO π
okay there's no SEE ALSO section in this one, but you can absolutely go read the ancestors listed up there in the OBJECT HIERARCHY, they're all right there, iykyk π§
and that's the whole page bestie, we ate, no crumbs π
this page is from perl v5.40.1, dated 2025-04-19, and it lives in the User Contributed Perl Documentation β mwah, kisses, go delete responsibly πβ¨
π¦ where this page comes from
- debian trixie: libnet-epp-perl 0.28-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu resolute: libnet-epp-perl 0.28-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu stonking: libnet-epp-perl 0.28-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms