On 11/05/13 05:18, Pearl Liang via RT wrote:
Dear Ken McDonell:
Thank you for your submission for a user port number. Please resolved
the following questions before we can process your requests.
1. You only provided the following:
Reference:
[http://oss.sgi.com/cgi-bin/gitweb.cgi?p=pcp/pcp.git;a=blob;f=man/man3/pmwebapi.3;hb=HEAD]
URLs are useful, but they might not be available in the future and
can be edited at any given time. IESG requires that the technical
description shall be documented in the application for future
reference purposes. Please document the service in this template.
Pearl,
Sorry, but I don't know how to amend/update the "template" ... I have
attached a text file that documents the WEBAPI. If you can insert that
into the template I'd be most grateful, else please advise how I can do
this.
2. Please explain why multiple allocations 44321, 44322, 44323 & 44324
are necessary. You may reply to this ticket for the current requests.
There are multiple processes and services in the suite of PCP tools,
each serving a different purpose.
44321 is for the protocol between the performance metrics collection
agent (pmcd) and any client requesting performance metrics.
44322 is for a proxy agent that provides access to one or more pmcds
behind a firewall.
44323 is for a web browser to collect performance data from web-client
aware server (pmwebd).
44324 is like 44323, but using secure connections ... so this has the
same relationship to 44323 that https (port 443) has to http (port 443).
So, they are different protocols involving different processes, but all
within the family of Performance Co-Pilot services and applications.
Please note the same answers and information apply to both IANA #679880
and IANA #679881, so for expediency I've replied here in a single email.
webapi.txt
Description: Text document
|