StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7539403
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-24T13:43:10.210
FavoriteCount
0
LastActivityDate
2011-09-24T13:43:10.210
LastEditDate
LastEditorUserId
0
OwnerUserId
244372
ParentId
7488748
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
For the server script, the dispatch_to method takes the path to the package to load, and the name of the package itself. If you pass a third parameter, it will limit the names of the methods made visible by the server. (e.g. 2 methods named <code>memory</code> and <code>time</code>, passing <code>Demo::time</code> as the 3rd param will make <code>memory</code> invisible to the client service.) File server.pl <pre><code>my $daemon = SOAP::Transport::HTTP::Daemon -> new (LocalPort => 801) -> dispatch_to('/home/soaplite/modules', 'Demo') ; </code></pre> Your Demo package should be a package with methods that return the values. I couldn't get Sys::MemInfo compiled on my system, so I just used localtime instead. I'm not sure why you named your package Demo.py, but Perl packages must have the extension pm, otherwise they won't be properly loaded. File Demo.pm <pre><code>#!/usr/bin/perl package Demo; #use Sys::MemInfo qw(totalmem freemem totalswap); sub memory { #print "total memory: ".(&totalmem / 1024)."\n"; return "Can't load Sys::MemInfo, sorry"; } sub time { my $time = localtime; return $time; } 1; </code></pre> For the client code, there's 2 important pieces that must be properly specified to work, the <code>proxy</code> and the <code>uri</code>. The proxy is the url path to the soap web service. Since you are running the server script as a daemon process, your path is just the web site's url. My computer doesn't have a url, so I used <code>http://localhost:801/</code>. The 801 is the port you specified above. If you were running as a cgi script inside of a different web server (such as Apache), then you would need to specify the cgi script to call (e.g. <code>http://localhost/cgi-bin/server.pl</code>, changing the package in server.pl to <code>SOAP::Transport::HTTP::CGI</code>. <code>uri</code> is probably the most confusing, but it's the namespace of the xml files returned by the web service. Turn on <code>+trace => 'debug'</code> to see the xml file returned by the web service. The uri should just be the name of the server. Even if you switch ports or to a cgi dispatch method, this uri stays the same. File test.pl <pre><code>#!perl -w use SOAP::Lite +trace => 'debug'; # Frontier http://www.userland.com/ $s = SOAP::Lite->new(proxy => 'http://superhonker.userland.com:801/', uri => 'http://superhonker.userland.com/'); #might be http://www.userland.com/ #but I could not test sub-domains print $s->time()->result; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to access a simple SOAP Service in Perl
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStreed
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to access a simple SOAP Service in Perl
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.