Call of Duty 4 Server Status 1.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Call of Duty 4 Server Status 1.0 (Default branch)
# 1  
Old 09-17-2008
Call of Duty 4 Server Status 1.0 (Default branch)

Call of Duty 4 Server Status is a PHP class can be used to retrieve information from Call Of Duty 4 game server. It connects to a Call Of Duty 4 server and retrieves information about the game status. The class stores game details like the players, scores, pings, etc. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Check the exit status in a pipe call

Guys, I have a problem :confused: and I need some help: I've to process many huge zip files. I'd code an application that receive the data from a pipe, so I can simple unzip the data and send it (via pipe) to my app. Something like that: gzip -dc <file> | app The problem is: How can I... (7 Replies)
Discussion started by: Rkolbe
7 Replies

2. UNIX for Dummies Questions & Answers

302 server status code to 301/404 server status code

Hello, Sorry for my english. I have an arcade site. mydomain.com/game.html If database has the game name is good. mydomain.com/fd43f54.html if database has not the game name redirect to mydomain.com by 302 error code. if database has not the game name i want a 301/404 error code and no... (0 Replies)
Discussion started by: hoo
0 Replies

3. UNIX for Advanced & Expert Users

Call parallel sql scripts from shell and return status when both sql are done

Hi Experts: I have a shell script that's kicked off by cron. Inside this shell script, I need to kick off two or more oracle sql scripts to process different groups of tables. And when both sql scripts are done, I will continue in the shell script to do other things like checking processing... (3 Replies)
Discussion started by: huasheng8
3 Replies
Login or Register to Ask a Question
RPC::pClient(3pm)					User Contributed Perl Documentation					 RPC::pClient(3pm)

NAME
RPC::pClient - Perl extension for writing pRPC clients SYNOPSIS
use RPC::pClient; $sock = IO::Socket::INET->new('PeerAddr' => 'joes.host.de', 'PeerPort' => 2570, 'Proto' => 'tcp'); $connection = new RPC::pClient('sock' => $sock, 'application' => 'My App', 'version' => '1.0', 'user' => 'joe', 'password' => 'hello!'); DESCRIPTION
pRPC (Perl RPC) is a package that simplifies the writing of Perl based client/server applications. RPC::pServer is the package used on the server side, and you guess what RPC::pClient is for. See RPC::pClient(3) for this part. pRPC works by defining a set of of functions that may be executed by the client. For example, the server might offer a function "multiply" to the client. Now a function call @result = $con->Call('multiply', $a, $b); on the client will be mapped to a corresponding call multiply($con, $data, $a, $b); on the server. (See the funcTable description below for $data.) The function calls result will be returned to the client and stored in the array @result. Simple, eh? :-) Client methods new The client constructor. Returns a client object or an error string, thus you typically use it like this: $client = RPC::pClient->new ( ... ); if (!ref($client)) { print STDERR "Error while creating client object: $client "; } else { # Do real stuff ... } Call calls a function on the server; the arguments are a function name, followed by function arguments. It returns the function results, if successfull. After executing Call() you should always check the error attribute: An empty string indicates success. Thus the equivalent to $c = Add($a, $b) # Use $c ... is $c = $client->Call("Add", $a, $b); if ($client->error) { # Do something in case of error ... } else { # Use $c ... } CallInt Similar to and internally used by Call. Receives the same arguments, but the result is prepended by a status value: If this status value is TRUE, then all went fine and the following result array is valid. Otherwise an error occurred and the error message follows immediately after the status code. Example: my($status, @result) = $client->CallInt("Add", $a, $b); if (!$status) { # Do something in case of error my $errmsg = shift @result || "Unknown error"; ... } else { ... } Encrypt This method can be used to get or set the cipher attribute, thus the encryption mode. If the method is passed an argument, the argument will be used as the new encryption mode. ('undef' for no encryption.) In either case the current encryption mode will be returned. Example: # Get the current encryption mode $mode = $server->Encrypt(); # Currently disable encryption $server->Encrypt(undef); # Switch back to the old mode $server->Encrypt($mode); Client attributes Client attributes will typically be supplied with the "new" constructor. sock An object of type IO::Socket, which should be connected to the server. cipher This attribute can be used to add encryption quite easily. pRPC is not bound to a certain encryption method, but to a block encryption API. The attribute is an object supporting the methods blocksize, encrypt and decrypt. For example, the modules Crypt::DES and Crypt::IDEA support such an interface. Note that you can set or remove encryption on the fly (putting "undef" as attribute value will stop encryption), but you have to be sure, that both sides change the encryption mode. Do not modify this attribute directly, use the encrypt method instead! However, it is legal to pass the attribute to the constructor. Example: use Crypt::DES; $crypt = DES->new(pack("H*", "0123456789abcdef")); $client->Encrypt($crypt); # or, to stop encryption $client->Encrypt(undef); application version user password it is part of the pRPC authorization process, that the client must obeye a login procedure where he will pass an application name, a protocol version and optionally a user name and password. You do not care for that (except passing the right values, of course :-), this is done within the client constructor. io this attribute is the Storable object created for communication with the server. You may use this, for example, when you want to change the encryption mode with Storable::Encrypt(). See Storable(3). EXAMPLE
#!/usr/local/bin/perl -T use 5.0004; # Yes, this really *is* required. use strict; # Always a good choice. use IO::Socket(); use RPC::pClient; # Constants my $MY_APPLICATION = "Test Application"; my $MY_VERSION = 1.0; my $MY_USER = "foo"; my $MY_PASSWORD = "bar"; # Connect to the server my $sock = IO::Socket::INET->new('PeerAddr' => 'joes.host.de', 'PeerPort' => 5000, 'Proto' => 'tcp'); if (!defined($sock)) { die "Cannot connect: $! "; } # Login procedure my $client = RPC::pClient->new('sock' => $sock, 'application' => $MY_APPLICATION, 'version' => $MY_VERSION, 'user' => $MY_USER, 'password' => $MY_PASSWORD); if (!ref($client)) { die "Cannot create client: $client "; } # Call multiply function my $a = $client->Call("multiply", 3, 4); if ($client->error) { die "An error occurred while multiplying: $a "; } AUTHOR
Jochen Wiedmann, wiedmann@neckar-alb.de SEE ALSO
pRPC::Server(3), Storable(3), Sys::Syslog(3) For an example application, see DBD::pNET(3). perl v5.10.1 1997-09-19 RPC::pClient(3pm)