File perl-Event-RPC.spec of Package perl-Event-RPC

Overview Repositories Revisions Requests Users Attributes Meta

File perl-Event-RPC.spec of Package perl-Event-RPC (Revision 5279903ea81e7b147c03ba65c0bf02ba)

Currently displaying revision 5279903ea81e7b147c03ba65c0bf02ba , Show latest

#
# spec file for package perl-Event-RPC
#
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#

Name:           perl-Event-RPC
Version:        1.05
Release:        0
%define cpan_name Event-RPC
Summary:        Event based transparent Client/Server RPC framework
License:        GPL-1.0+ or Artistic-1.0
Group:          Development/Libraries/Perl
Url:            http://search.cpan.org/dist/Event-RPC/
Source:         http://www.cpan.org/authors/id/J/JR/JRED/%{cpan_name}-%{version}.tar.gz
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(Event)
BuildRequires:  perl(Glib)
BuildRequires:  perl(IO::Socket::SSL)
BuildRequires:  perl(Net::SSLeay)
Requires:       perl(Event)
Requires:       perl(Glib)
Requires:       perl(IO::Socket::SSL)
Requires:       perl(Net::SSLeay)
%{perl_requires}

%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 %{cpan_name}-%{version}
find . -type f -print0 | xargs -0 chmod 644

%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}

%check
%{__make} test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%files -f %{name}.files
%defattr(-,root,root,755)
%doc Changes examples README

%changelog

Places

File perl-Event-RPC.spec of Package perl-Event-RPC (Revision 5279903ea81e7b147c03ba65c0bf02ba)

Places