Doing a HAS-A probably would be better, or...
I could provide two constructors in the base class, 1) that would return a blessed scalar (the apache session ID), and another for local use, determined by caller(), that returns a blessed hash... that sounds like fun!
sub joe_method {
my $self = ref ($_[0] eq 'SCALAR') ? getSessionHashRef(shift) : sh
+ift;
# getSessionHashRef exists in base class, or...
# MyApacheSessionHelper->getSessionHashRef (shift)
...
}
Actually, calling by RPC, the 1st arg would be (for me) SOAP::Lite. So the above should be:
sub joe_method {
my $self = ref (shift eq 'SOAP::Lite') ? getSessionHashRef(shift)
+: $_;
...
}
The blessed scaler (the sessionID) would be usefull for a proxy class -- wrapper for the RPC call -- client-side.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.