Sponsored Content
Top Forums Web Development Notes with Ravinder on Badging System Development Part II Post 303028268 by Neo on Thursday 3rd of January 2019 07:22:04 AM
Old 01-03-2019
Update:

41 of 48 prototype badges done, or 85%.

Ravinder is working on the logic for a "consecutive days or forum activity" badge, which sounds cool, so that would be number 42 I guess, which will leave 6 "Reserved" badges left to do.

If one of those "Reserved" badges is allocated for the the mod system of member ranking; then that means:

Code:
41 Badges Done
1 Badge Under Development (Ravinder)
1 Badge for Mod Scoring / Points (Reserved)

This is real progress in a relatively short time.

If anyone has an idea for a badge, please post!

Thanks.
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid: https://www.unix.com/members/1-albums215-picture991.png The prototype HTML code for this layout: <style> .fa-badge-grid { font-size: 1.5em; } .row { ... (38 Replies)
Discussion started by: Neo
38 Replies

2. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

Badging System: UNIX.COM Bug Hunter Badge (New)

I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
dat_rsp_create(3DAT)				     Direct Access Transport Library Functions				      dat_rsp_create(3DAT)

NAME
dat_rsp_create - create a Reserved Service Point SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_rsp_create ( IN DAT_IA_HANDLE ia_handle, IN DAT_CONN_QUAL conn_qual, IN DAT_EP_HANDLE ep_handle, IN DAT_EVD_HANDLE evd_handle, OUT DAT_RSP_HANDLE *rsp_handle ) PARAMETERS
ia_handle Handle for an instance of DAT IA. conn_qual Connection Qualifier of the IA the Reserved Service Point listens to. ep_handle Handle for the Endpoint associated with the Reserved Service Point that is the only Endpoint that can accept a Connection Request on this Service Point. The value DAT_HANDLE_NULL requests the Provider to associate a Provider-created Endpoint with this Service Point. evd_handle The Event Dispatcher to which an event of Connection Request arrival is generated. rsp_handle Handle to an opaque Reserved Service Point. DESCRIPTION
The dat_rsp_create() function creates a Reserved Service Point with the specified Endpoint that generates, at most, one Connection Request that is delivered to the specified Event Dispatcher in a Notification event. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INSUFFICIENT_RESOURCES The operation failed due to resource limitations. DAT_INVALID_HANDLE The ia_handle, evd_handle, or ep_handle parameter is invalid. DAT_INVALID_PARAMETER The conn_qual parameter is invalid. DAT_INVALID_STATE Parameter in an invalid state. For example, an Endpoint was not in the Idle state. DAT_CONN_QUAL_IN_USE Specified Connection Qualifier is in use. USAGE
The usage of a Reserve Service Point is as follows: o The DAT Consumer creates a Local Endpoint and configures it appropriately. o The DAT Consumer creates a Reserved Service Point specifying the Local Endpoint. o The Reserved Service Point performs the following: o Collects native transport information reflecting a received Connection Request. o Creates a Pending Connection Request. o Creates a Connection Request Notice (event) that includes the Pending Connection Request (which includes, among others, Reserved Service Point Connection Qualifier, its Local Endpoint, and information about remote Endpoint). o Delivers the Connection Request Notice to the Consumer-specified target (CNO) evd_handle. The Local Endpoint is transitioned from Reserved to Passive Connection Pending state. o Upon receiving a connection request, or at some time subsequent to that, the DAT Consumer must either accept() or reject() the Pending Connection Request. o If accepted, the original Local Endpoint is now in a Connected state and fully usable for this connection, pending only native transport mandated RTU messages. This includes binding it to the IA port if that was not done previously. The Consumer is noti- fied that the Endpoint is in a Connected state by a Connection Established Event on the Endpoint connect_evd_handle. o If rejected, the Local Endpoint point transitions into Unconnected state. The DAT Consumer can elect to destroy it or reuse it for other purposes. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.11 16 Jul 2004 dat_rsp_create(3DAT)
All times are GMT -4. The time now is 06:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy