[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dev-serveez] progress to serveez-0.2

From: Thien-Thi Nguyen
Subject: Re: [dev-serveez] progress to serveez-0.2
Date: Mon, 05 Nov 2012 09:21:18 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux)

() Julian Graham <address@hidden>
() Sun, 4 Nov 2012 22:09:55 -0500

   Since my implementation was originally derived from digging around in
   the guts of the libserveez code, I'm happy to rewrite my stuff to do
   things the blessed way -- whatever that is -- but in case any of the
   above is a surprise to you I wanted to make sure you knew.

Well, better late than never (like Serveez, itself).  Let's see here...

   * svz_coserver_types

I can't find this symbol anywhere in the repo (past or present).  What
is its role in your program?  Which Serveez version are you digging
around in?

   * svz_server_finalize_all
   * svz_server_init_all

These have been combined into ‘svz_updn_all_servers’.  See (static func)
‘guile_entry’ in src/serveez.c for details.  But see below first.

   * svz_portcfg_prepare
   * svz_server_instantiate
   * svz_server_create
   * svz_server_add

These have been "internalized".  I think the blessed way now is to avoid
this sort of imperative plumbing and specify things in Scheme, and/or at
a higher level.  For instance, ‘svz_portcfg_prepare’ is now called by
‘svz_server_bind’, which is part of the API, and furthermore exposed to
Scheme as part of procedure ‘bind-server!’.  See test/t00[1234] for good
examples, test/t006 for bad (i.e., PEBKAC situation).

[cc trimmed]
Thien-Thi Nguyen ..................................... GPG key: 4C807502
.                  NB: ttn at glug dot org is not me                   .
.                 (and has not been since 2007 or so)                  .
.                        ACCEPT NO SUBSTITUTES                         .
........... please send technical questions to mailing lists ...........

Attachment: pgph2WCWFj6Vw.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]