perl/perl-HTTP-Server-Simple
SHA256
8
0
Fork 0
forked from pool/perl-HTTP-Server-Simple
Code Pull Requests Activity

Accepting request 484289 from devel:languages:perl:autoupdate

Browse Source 
automatic update

OBS-URL: https://build.opensuse.org/request/show/484289
OBS-URL: https://build.opensuse.org/package/show/devel:languages:perl/perl-HTTP-Server-Simple?expand=0&rev=21
This commit is contained in:
Stephan Kulow
2017-04-06 13:04:17 +00:00
committed by Git OBS Bridge
parent 3adae98c18
commit ebc032e594
4 changed files with 27 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
perl-HTTP-Server-Simple.spec
View File

@@ -1,7 +1,7 @@
#
# spec file for package perl-HTTP-Server-Simple
#
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
# Copyright (c) 2017 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
@@ -17,14 +17,14 @@
Name: perl-HTTP-Server-Simple
Version: 0.51
Version: 0.52
Release: 0
%define cpan_name HTTP-Server-Simple
Summary: Lightweight HTTP server
License: Artistic-1.0 or GPL-1.0+
Group: Development/Libraries/Perl
Url: http://search.cpan.org/dist/HTTP-Server-Simple/
Source0: http://www.cpan.org/authors/id/B/BP/BPS/%{cpan_name}-%{version}.tar.gz
Source0: https://cpan.metacpan.org/authors/id/B/BP/BPS/%{cpan_name}-%{version}.tar.gz
Source1: cpanspec.yml
BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -44,27 +44,26 @@ This is a simple standalone HTTP server. By default, it doesn't thread or
fork. It does, however, act as a simple frontend which can be used to build
a standalone web-based application or turn a CGI into one.
It is possible to use the Net::Server manpage classes to create forking,
pre-forking, and other types of more complicated servers; see the
/net_server manpage.
It is possible to use Net::Server classes to create forking, pre-forking,
and other types of more complicated servers; see net_server.
By default, the server traps a few signals:
* HUP
When you 'kill -HUP' the server, it lets the current request finish being
processed, then uses the 'restart' method to re-exec itself. Please note
that in order to provide restart-on-SIGHUP, HTTP::Server::Simple sets a
SIGHUP handler during initialisation. If your request handling code forks
you need to make sure you reset this or unexpected things will happen if
somebody sends a HUP to all running processes spawned by your app (e.g.
by "kill -HUP <script>")
When you 'kill -HUP' the server, it lets the current request finish being
processed, then uses the 'restart' method to re-exec itself. Please note
that in order to provide restart-on-SIGHUP, HTTP::Server::Simple sets a
SIGHUP handler during initialisation. If your request handling code forks
you need to make sure you reset this or unexpected things will happen if
somebody sends a HUP to all running processes spawned by your app (e.g. by
"kill -HUP <script>")
* PIPE
If the server detects a broken pipe while writing output to the client,
it ignores the signal. Otherwise, a client closing the connection early
could kill the server.
If the server detects a broken pipe while writing output to the client, it
ignores the signal. Otherwise, a client closing the connection early could
kill the server.
%prep
%setup -q -n %{cpan_name}-%{version}