AMF-Perl
view release on metacpan or search on metacpan
doc/examples/petmarket/petmarket/api/cartservice.pm view on Meta::CPAN
},
"getCreditCards" => {
"description" => "Returns list of allowed credit cards.",
"access" => "remote",
},
"getShippingMethods" => {
"description" => "Returns list of shipping methods.",
"access" => "remote",
"returns" => "AMFObject"
},
"validateCartOID" => {
"description" => "Validate that the supplied rat OID is good.",
"access" => "remote",
},
"getCartItems" => {
"description" => "List the items in the cart with the given ID",
"access" => "remote",
"returns" => "AMFObject"
},
"getCartTotal" => {
"description" => "Return the total number of items and total cost of the cart with the given ID",
doc/examples/petmarket/petmarket/api/cartservice.pm view on Meta::CPAN
push @row, $descriptions[$i];
push @row, $prices[$i];
push @row, $days[$i];
push @methods, \@row;
}
return AMF::Perl::Util::Object->pseudo_query(\@columns, \@methods);
}
sub validateCartOID
{
my ($self, $id) = @_;
return $id;
}
sub newCart
{
my ($self) = @_;
my ($id, $count);
do
lib/AMF/Perl/IO/Serializer.pm view on Meta::CPAN
#Only arrayrefs and hashrefs will work
# were still lacking dates, xml, and strings longer than 65536 chars
sub writeData
{
my ($self, $d, $type)=@_;
$type = "unknown" unless $type;
# **************** TO DO **********************
# Since we are now allowing the user to determine
# the datatype we have to validate the user's suggestion
# vs. the actual data being passed and throw an error
# if things don't check out.!!!!
# **********************************************
# get the type of the data by checking its reference name
#if it was not explicitly passed
if ($type eq "unknown")
{
if (!defined $d) # convert undef to null, but not "" or 0
{
( run in 0.250 second using v1.01-cache-2.11-cpan-a5abf4f5562 )