Sponsored Content
Full Discussion: UltraSPARC T2 or T2+
Special Forums Hardware UltraSPARC T2 or T2+ Post 302421370 by soliberus on Friday 14th of May 2010 07:39:52 AM
Old 05-14-2010
Crikey, that's going to be expensive to licence then.

Thanks for the quick response.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

printing with my UltraSparc

I just got an HP 1200se printer. I have it networked using a single print server, so I'd really like to get it working with my Ultra10 system. I know that there are no Solaris drivers, honestly, I don't know if HP puts out Solaris drivers for any of their stuff. This printer, and I dunno... (2 Replies)
Discussion started by: xyyz
2 Replies

2. UNIX Benchmarks

Sun Blade 2000 UltraSparc III Solaris 8

Sun Blade 2000 UltraSparc III Solaris 8 Notes: prtdiag: System Configuration: Sun Microsystems sun4u SUNW,Sun-Blade-1000 (UltraSPARC-III+) System clock frequency: 150 MHZ Memory size: 3GB ==================================== CPUs ==================================== ... (0 Replies)
Discussion started by: tnorth
0 Replies

3. Solaris

440 MHz problems in UltraSparc 5 Computer

Hi all, I recently purchased a 440 MHz processor module for my Sun Ultrasparc 5 computer. I installed the module, updated the boot prom to the most recent version and when the machine starts up the initial white screen shows I have a 333 MHz processor installed ! I checked the details of the... (2 Replies)
Discussion started by: usparche
2 Replies

4. Solaris

First posting Help :ULTRA 10 UltraSPARC-IIi 360MHZ

Hello Forum team members, I have a problem with ULTRA 10. It does not boot and just stops at this prompt. OpenBoot 3.19, 256 MB... Boot device:disk:a File and args: Need your help, Thanks in advance, Regards NV. (7 Replies)
Discussion started by: narahv
7 Replies
Perlbal::Plugin::Cgilike(3pm)				User Contributed Perl Documentation			     Perlbal::Plugin::Cgilike(3pm)

NAME
Perlbal::Plugin::Cgilike - Handle Perlbal requests with a Perl subroutine DESCRIPTION
This module allows responses to be handled with a simple API that's similar in principle to CGI, mod_perl response handlers, etc. It does not, however, come anywhere close to conforming to the CGI "standard". It's actually more like mod_perl in usage, though there are several differences. Most notably, Perlbal is single-process and single-threaded, and handlers run inside the Perlbal process and must therefore return quickly and not do any blocking operations. As it currently stands, this is very bare-bones and has only really been used with basic GET requests. It lacks a nice API for handling the body of a POST or PUT request. It is not recommended to use this for extensive applications. Perlbal is first and foremost a load balancer, so if you're doing something at all complicated you're probably better off using something like Apache mod_perl and then putting Perlbal in front if it if necessary. However, this plugin may prove useful for simple handlers or perhaps embedding a simple HTTP service into another application that uses "Danga::Socket". SYNOPSIS
This module provides a Perlbal plugin which can be loaded and used as follows. LOAD cgilike PERLREQUIRE = MyPackage CREATE SERVICE cgilike SET role = web_server SET listen = 127.0.0.1:80 SET plugins = cgilike PERLHANDLER = MyPackage::handler ENABLE cgilike With this plugin loaded into a particular service, the plugin will then be called for all requests for that service. Set cgilike.handler to the name of a subroutine that will handle requests. This subroutine will receive an object which allows interaction with the Perlbal service. package MyPackage sub handler { my ($r) = @_; if ($r->uri eq '/') { print "<p>Hello, world</p>"; return Perlbal::Plugin::Cgilike::HANDLED; } else { return 404; } } Return "Perlbal::Plugin::Cgilike::HANDLED" to indicate that the request has been handled, or return some HTTP error code to produce a predefined error message. You may also return "Perlbal::Plugin::Cgilike::DECLINED" if you do not wish to handle the request, in which case Perlbal will be allowed to handle the request in whatever way it would have done without Cgilike loaded. If your handler returns any non-success value, it MUST NOT produce any output. If you produce output before returning such a value, the response to the client is likely to be utter nonsense. You may also return "Perlbal::Plugin::Cgilike::POSTPONE_RESPONSE", which is equivalent to returning zero except that the HTTP connection will be left open once you return. It is your responsibility to later call "$r->end_response()" when you have completed the response. This style is necessary when you need to perform some long operation before you can return a response; you'll need to use some appropriate method to set a callback to run when the operation completes and then do your response in the callback. Once you've called "end_response", you must not call any further methods on $r; it's probably safest to just return immediately afterwards to avoid any mishaps. API DOCUMENTATION
TODO: Write this TODO
Currently there is no API for dealing with the body of a POST or PUT request. Ideally it'd be able to do automatic decoding of application/x-www-form-urlencoded data, too. The POSTPONE_RESPONSE functionality has not been tested extensively and is probably buggy. COPYRIGHT AND LICENSE
Copyright 2007 Martin Atkins <mart@degeneration.co.uk> and Six Apart Ltd. This module is part of the Perlbal distribution, and as such can be distributed under the same licence terms as the rest of Perlbal. perl v5.14.2 2010-12-20 Perlbal::Plugin::Cgilike(3pm)
All times are GMT -4. The time now is 11:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy