Group :: Development/Perl
RPM: perl-Event-RPC
Navigation
Main Changelog Spec Patches Sources Download Gear Bugs and FR Repocop
#
# - Event::RPC -
# This spec file was automatically generated by cpan2rpm [ver: 2.027]
# (ALT Linux revision)
# The following arguments were used:
# Event::RPC
# For more information on cpan2rpm please visit: http://perl.arix.com/
#
%define module Event-RPC
%define m_distro Event-RPC
%define m_name Event::RPC
%define m_author_id unknown
%define _enable_test 1
Name: perl-Event-RPC
Version: 0.90
Release: alt1
Summary: Event based transparent Client/Server RPC framework
License: Artistic
Group: Development/Perl
Url: http://www.cpan.org
Packager: Vitaly Lipatov <lav at altlinux.ru>
BuildArch: noarch
Source: http://search.cpan.org//CPAN/authors/id/J/JR/JRED/%m_distro-%version.tar.gz
# Automatically added by buildreq on Tue Jan 03 2006
BuildRequires: perl-Event perl-Glib perl-IO-Socket-SSL perl-Log-Agent perl-Net-SSLeay perl-Storable perl-devel
%description
Event::RPC consists of a server and a client library. The server exports a list of classes and methods, which are allowed to be called over the network. More specific it acts as a proxy for objects created on the server side (on demand of the connected clients) which handles client side methods calls with transport of method arguments and return values.
The object proxy handles refcounting and destruction of objects created by clients properly. Objects as method parameters and return values are handled as well (although with some limitations, see below).
For the client the whole thing is totally transparent - once connected to the server it doesn't know whether it calls methods on local or remote objects.
Also the methods on the server newer know whether they are called locally
or from a connected client. Your application logic is not affected by Event::RPC at all, at least if it has a rudimentary clean OO design.
For details on implementing servers and clients please refer to the man pages of Event::RPC::Server and Event::RPC::Client.
%prep
%setup -q -n %m_distro-%version
%build
%perl_vendor_build
%install
%perl_vendor_install
%files
%doc Changes README
%perl_vendor_privlib/*
%perl_vendor_man3dir/*
%changelog
…
Full changelog you can see here
# - Event::RPC -
# This spec file was automatically generated by cpan2rpm [ver: 2.027]
# (ALT Linux revision)
# The following arguments were used:
# Event::RPC
# For more information on cpan2rpm please visit: http://perl.arix.com/
#
%define module Event-RPC
%define m_distro Event-RPC
%define m_name Event::RPC
%define m_author_id unknown
%define _enable_test 1
Name: perl-Event-RPC
Version: 0.90
Release: alt1
Summary: Event based transparent Client/Server RPC framework
License: Artistic
Group: Development/Perl
Url: http://www.cpan.org
Packager: Vitaly Lipatov <lav at altlinux.ru>
BuildArch: noarch
Source: http://search.cpan.org//CPAN/authors/id/J/JR/JRED/%m_distro-%version.tar.gz
# Automatically added by buildreq on Tue Jan 03 2006
BuildRequires: perl-Event perl-Glib perl-IO-Socket-SSL perl-Log-Agent perl-Net-SSLeay perl-Storable perl-devel
%description
Event::RPC consists of a server and a client library. The server exports a list of classes and methods, which are allowed to be called over the network. More specific it acts as a proxy for objects created on the server side (on demand of the connected clients) which handles client side methods calls with transport of method arguments and return values.
The object proxy handles refcounting and destruction of objects created by clients properly. Objects as method parameters and return values are handled as well (although with some limitations, see below).
For the client the whole thing is totally transparent - once connected to the server it doesn't know whether it calls methods on local or remote objects.
Also the methods on the server newer know whether they are called locally
or from a connected client. Your application logic is not affected by Event::RPC at all, at least if it has a rudimentary clean OO design.
For details on implementing servers and clients please refer to the man pages of Event::RPC::Server and Event::RPC::Client.
%prep
%setup -q -n %m_distro-%version
%build
%perl_vendor_build
%install
%perl_vendor_install
%files
%doc Changes README
%perl_vendor_privlib/*
%perl_vendor_man3dir/*
%changelog
…
Full changelog you can see here