10 More Discussions You Might Find Interesting
1. Solaris
Java web console Vs Web-Based Enterprise Management(WBEM)
1. I like to understand the difference in purpose of using java web console and Web-Based Enterprise Management (WBEM)
2. As per CIS benchmark, both of them has to be disabled when not used for increased security.
Solaris admin(s) -... (0 Replies)
Discussion started by: cyberidude
0 Replies
2. Solaris
Dear Team
please some body know what happened with smcwebconsole from Solaris10 to Solaris11 I don't found this script or Don't find in svcs -a
please if some body know any think about this issue to tell us
best, :p (2 Replies)
Discussion started by: Hosam
2 Replies
3. Solaris
i need how to use graphical user interface for zfs using web console ,
thanks (3 Replies)
Discussion started by: Amr
3 Replies
4. UNIX for Dummies Questions & Answers
Hi everyone-
I'm relatively new to UNIX (Primarily Oracle background), wondering if anyone can help me.
I did not configure Oracle Database Control (Web-Based admin interface) on the Database Server (HP-UX), however it is running and the URL is configured with an internal IP, which users have... (4 Replies)
Discussion started by: campbellg
4 Replies
5. HP-UX
I have firmware 2.0 for the HP Secure Web Console, but looking for 1.8. Hp does not have this posted anywhere. Anyone have it? Thanks. (0 Replies)
Discussion started by: mrmurdock
0 Replies
6. Red Hat
Hi,
I am very bad at scripting. I need help from scripting experts...
I need to change password of around 100 linux remote servers. I have been given a script for changing the password that automates the task. however I do not understand the usage and meaning of the script, the script is an... (0 Replies)
Discussion started by: renuka
0 Replies
7. Solaris
All,
I am trying to get the Sun Web Console to work with ZFS and am not getting anywhere. When I first tried to get the web console https://server:6789/zfs it gave me a page can't be displayed (500 error). I've played around and performed the following and can now get it to log in and display... (7 Replies)
Discussion started by: darkoth
7 Replies
8. UNIX for Advanced & Expert Users
I am supporting a little over 300+ servers, mostly Solaris with a handful of AIX and HPUX. Currently each box has its own sudoers file that is different. I have ran a script and captured each sudoers file. Our goal is to have 1 common sudo file on a trusted host and then only have to edit that file... (4 Replies)
Discussion started by: Gibby13
4 Replies
9. Shell Programming and Scripting
Hi there--I think this is more of a Windows question, but I think many of you might be able to help me out:
I have a UNIX web server and a Windows machine. I'm trying to script the following tasks so that they can be run from the Windows machine (via a
batch file):
1. Shutdown web services... (5 Replies)
Discussion started by: sohungry73
5 Replies
10. UNIX for Advanced & Expert Users
I'm really sorry to bother you all but does anyone know a good web site for learning how to buid a web server.
I have to use 1 to connect to my database,
yes I am a student......please help. (1 Reply)
Discussion started by: spiderman
1 Replies
Jifty::Web::PageRegion(3pm) User Contributed Perl Documentation Jifty::Web::PageRegion(3pm)
NAME
Jifty::Web::PageRegion - Defines a page region
DESCRIPTION
Describes a region of the page which contains a Mason fragment which can be updated via AJAX or via query parameters.
new PARAMHASH
Creates a new page region. The possible arguments in the "PARAMHASH" are:
name
The (unqualified) name of the region. This is used to generate a unique id -- it should consist of only letters and numbers.
path
The path to the fragment that this page region contains. Defaults to "/__jifty/empty", which, as its name implies, is empty.
arguments (optional) (formerly 'defaults')
Specifies an optional set of parameter defaults. These should all be simple scalars, as they might be passed across HTTP if AJAX is
used.
See Jifty::Web::Form::Element for a list of the supported parameters.
force_arguments (optional)
Specifies an optional set of parameter values. They will override anything sent by the user or set via AJAX.
force_path (optional)
A fixed path to the fragment that this page region contains. Overrides anything set by the user.
parent (optional)
The parent Jifty::Web::PageRegion that this region is enclosed in.
region_wrapper (optional)
A boolean; whether or not the region, when rendered, will include the HTML region preamble that makes Javascript aware of its presence.
Defaults to true.
lazy (optional)
Delays the loading of the fragment until client render-time. Obviously, does not work with downlevel browsers which don't support
javascript.
loading_path (optional)
The fragment to display while the client fetches the actual region. Make this lightweight, or you'll be losing most of the benefits of
lazy loading!
name [NAME]
Gets or sets the name of the page region.
qualified_name [NAME]
Gets or sets the fully qualified name of the page region. This should be unique on a page. This is usually set by "enter", based on the
page regions that this region is inside. See "qualified_region" in Jifty::Web.
default_path [PATH]
Gets or sets the default path of the fragment. This is overridden by "path".
path [PATH]
Gets or sets the path that the fragment actually contains. This overrides "default_path".
default_argument NAME [VALUE]
Gets or sets the default value of the "NAME" argument. This is used as a fallback, and also to allow generated links to minimize the
amount of state they must transmit.
argument NAME [VALUE]
Gets or sets the actual run-time value of the page region. This usually comes from HTTP parameters. It overrides the "default_argument"
of the same "NAME".
arguments [HASHREF]
Sets all arguments at once, or returns all arguments. The latter will also include all default arguments.
enter
Enters the region; this sets the qualified name based on "qualified_region" in Jifty::Web, and uses that to pull runtime values for the
"path" and "argument"s from the "state_variables" in Jifty::Request before overriding them with the "force" versions.
exit
Exits the page region, if it is the most recent one. Normally, you won't need to call this by hand; however, if you are calling "enter" by
hand, you will need to call the corresponding "exit".
as_string
Deals with the bulk of the effort to show a page region. Returns a string of the fragment and associated javascript (if any).
render
Calls "enter", outputs the results of "as_string", and then calls "exit". Returns an empty string.
make_body
Outputs the results of the region to the current buffer.
render_as_subrequest
get_element [RULES]
Returns a CSS2 selector which selects only elements under this region which fit the "RULES". This method is used by AJAX code to specify
where to add new regions.
client_cacheable
Returns the client cacheable state of the regions path. Returns false if the template has not been marked as client cacheable. Otherwise it
returns the string "static" or "action" based on the cacheable attribute set on the template.
client_cache_content
Returns the template as JavaScript code.
perl v5.14.2 2010-12-08 Jifty::Web::PageRegion(3pm)