Hey Jame!

Feb 09 15:01 05, Jame Clay wrote to Maurice Kinal:

 JC>    Only briefly, but I haven't had a chance to try incorporateing 
 JC> it...  Nor
 JC> did you mention where you used it...  As a replacement for the 
 JC> subroutine?

No.  I just used it as a substitue to calculate DateTime.  I thought I said
that in the message I sent.  I'll look later at which line in the original
script and post both here.  Sound okay?

 JC>   I gather that it requires hat it requires the Posix module?  That 
 JC> brings up
 JC> the question (for me) of how standard is that module for Perl 
 JC> installations...

It is a standard module with the generic Perl install.  Any Linux
distribution should have it at their disposal.  The only ones I plan to use
that aren't part of the standard Perl are the XML modules but I haven't
encorporated them yet.  What I may do instead is work with the script as is
before porting it over to a XML-RPC function.  It is good as is (especially
with the one edit) but I'd like it to be a bit more lean and add a loop for
multiple messages.  Works great as a "Daily Fortune" thingy on
the BBS.  I like it.

 JC>     Sounds interesting!  How do you plan to interface to it?  

Myself?  Other then testing and stuff I probably won't.  The thing is I am
a hardcore text/console type guy and prefer that.  However I have some
interested parties who would like to be able to interface with their
browsers.  The thing is that a XML-RPC server does't require any particular
scripting language to successfully communicate with it so people could use
Javascript to do that which is common to most web browsers.

 JC>     I'd  certainly be interested in seeing it!

 JC>     And do you have a Sourceforge account?   If so, could add what 
 JC> you are
 JC> doing to the ftnpl project there...  

Yes but I have long since forgotten the password.  They still send me stuff
via email but I haven't used Sourceforge in quite some time.  What for?

I could netmail you the modified script once I am happy with it.  I am
still hung up on the MSGID but I could leave that as is and increment it
inside the loop when there are multiple messages.  As of this writing I am
still undecided other then I wish it to actually mean something, such as
the hex ddhhmmss.  As is that isn't going to survive too much longer or at
least not on the LAN.  At the very least I'd tack on yy to the beginning
and then increment ss by one each pass, through the loop.  That will make
it good for at least 100 years as far as ensuring uniqueness, probably
longer, and speed up dupe checking if the tossing part only needs to check
the archive(s) in a particular range of MSGID's without even requiring to
know the date seeing it is encorporated.  That will work for this node
anyhow.  The rest?  Dog eat dog I guess.  :-/

I probably won't bother scanning inbound for dupes.  What for?  No standard
to work with and all of the headers will be completely stripped out anyhow
to any user's or clients inbound seeing as none of that matters to them.  I
am not sure what the XML-RPC server will do with it other then to add REPLY
etc. kludges when appropriate to do so.  A real bore's nest eh?

Life is good,
Maurice

--- Msged/LNX 6.1.2