Project

General

Profile

Feature #1329

Add support for CAP Server-Time

Added by Moter8 almost 8 years ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/01/2015
Due date:
% Done:

0%

Estimated time:
OS:
Any

Description

As specified in https://github.com/ircv3/ircv3-specifications/blob/master/extensions/server-time-3.2.md

Would help making these: http://i.imgur.com/bJq7ArF.png time tags to not appear at all [These are added from ZNC due to quassel not supporting CAP server-time]

History

#1 Updated by Avamander almost 4 years ago

There was some talk in the IRC channel that some people are planning to implement this. I'm just commenting to show that there's users who would like to use this feature.

#2 Updated by justjanne almost 4 years ago

This feature has been implemented, and is waiting to be merged: https://github.com/quassel/quassel/pull/479

#3 Updated by Sandybradford 2 days ago

A Node.js CAP server process is started with the cds serve CLI command, with cds run and cds watch as convenience variants.

Besides, handling command line arguments and adding log output, cds serve essentially loads a built-in server.js module, which can be accessed through cds.server.

You can plug-in custom logic to the default bootstrapping choreography using a custom server.jsin your project.

cds serve command line
cds.server → (options) => {…}
Built-in server.js
Custom server.js
cds.once (‘bootstrap’, (express.js app)=>{})
cds.on (‘loaded’, (csn)=>{})
cds.on (‘connect’, (service)=>{})
cds.on (‘serving’, (service)=>{})
cds.once (‘served’, (services)=>{})
cds.once (‘listening’, ({server,url})=>{})
cds.serve… ⇢ service(s)
cds.serve (service, options) → fluent api…
↳ .from (model)
↳ .to (protocol)
↳ .at (path)
↳ .in (express app)
↳ .with (impl function)
https://www.mypennmedicine.ltd/

Also available in: Atom PDF