Re: CLJ newsgroup FAQ

Jim Ley wrote:

On 23 Jul 2006 01:48:30 -0700, "Bart Van der Donck" <bart@xxxxxxxxxx>
wrote:

(1) If the owner of an interested website is willing to give
username/password (S/FTP), then the software at my end could
automatically replace the file on a daily base. This does not require
any extra tools, as I assume all websites are accessible by FTP one way
or another. Of course I can understand that not all website owners are
willing to share their FTP login data.

I certainly wouldn't make a website available to FTP, and I see no
reason to provide FTP simply to have SFTP when there are much better
methods.

The bigger problem with automatic updating of content generated from
an unknown webapp that allows html input, is avoiding insertion
attacks, or even simply avoiding spam - web versions of FAQ's tend to
be high ranked so well worth getting links on.
[...]

Another (better?) project description could maybe consist of the
following:

- Crontab file starts up Perl program once a day
- Perl program grabs http://www.jibbering.com/faq/index.xml
- Checks on successful GET-request, valid XML, well-formed XML,
security, etc.
- Determine which FAQ-entry is to send to Usenet
- Parse XML and extract the part we need
- Format message towards Usenet and fire it off
- Keep track of which FAQ is to be sent next time (number)
- Exit

Of course, this scenario is simpler as my initial proposal. It doesn't
touch anything about the way the current FAQ (or its
maintainance/structure/contents) works. It's just an add-on that is
responsible for the sending of one-FAQ-entry-a-day, and that's it.

I investigated the structure of http://www.jibbering.com/faq/index.xml,
this should be suitable; some questions:

- What does the "hash"-argument of the <URL> tag mean ?

- As Richard said, the code examples should be adapted in the data so
that it doesn't exceed 68 characters per line.

- It should be logical that each FAQ-entry would have its number in the
XML-data as well. This would be easier for Perl to remember which
FAQ-entry is to send the next day. Now Perl needs to invent its own
counting mechanism to determine which FAQ-entry is to send out. (which
shouldn't be a problem technically though, so generally this point is
only a side-remark). But when new entries are added in the future, this
might at some point result in a jump/reverse in the counting mechanism.
I don't know about the possibilities of something like
<FAQNR>4.22</FAQNR> or <CONTENT FAQNR="4.22">.

- As a professional pedantrist, it would be better practice to start
with <?xml version="1.0" encoding="UTF-8"?> , use some DTD/schema
info and do
<CHAPTER TITLE="Quick Answers" CHAPNR="4">
in stead of
<CONTENT TITLE="Quick Answers">
and perhaps
<FAQENTRY TITLE="What is ECMAScript?" ENTRYNR="7">
in stead of
<CONTENT TITLE="What is ECMAScript?">
to get the touch of real XML-ish structurisation. If you want to, I
could adapt the XML file that way. But the current XML structure is
suitable as well (these are optimisation issues only).

--
Bart

.

Relevant Pages

  • VFP 9: Help with sending/receiving XML via FTP
    ... Looking for resources which will help me understand XML via FTP. ... Recipient checks FTP folder for contents. ... Confirmation is returned to sender. ...
    (microsoft.public.fox.programmer.exchange)
  • Binary message creation in BizTalk Server
    ... Setup a new orchestration and drop a rcv shape and port in there in order ... Iterate through each of the vendors in your inbound XML message ... - assign the FTP username and password to use in the construct message ...
    (microsoft.public.biztalk.general)
  • Re: FTP and XML
    ... XML with FTP. ... XML is nothing but text. ... the client can ... which transactions belong to him. ...
    (microsoft.public.fox.programmer.exchange)
  • What do you call to create XML/Soap to send to a remote WS?
    ... don't know what I need to query my database with that will form the same XML? ... I want this process to run at rergular intervals similar to a scheduled DTS pkg ... confirmation via FTP, I cannot expose a public ws, so for the order confirmation ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: XML to FTP
    ... > preassigned location. ... You can use the built in function to create an xml file. ... to make your ftp function. ...
    (microsoft.public.access.modulesdaovba)