Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Hello Folks, Yet Another New Feature announcement....

I've made some changes and "improvements" to the Private Message XML Ticker that will hopefully allow folks to make better CB clients, and also which should in the long term allow us to reduce the server load that feeding all those CB clients causes.

The changes for now should make no difference to anyone using proper XML parsing techniques. However by August 1, 2004 we will put in place a restriction on the number of records that will be returned by the ticker. At this point any client expecting to get all of their private messages from a single fetch will no longer work.

The main changes are to the interface. We now support a number of extra arguments. They are as follows:

xmlstyle
Currently this may be 'clean' or 'default', anything else including omitting the paramater will be treated as though it were 'default'. In 'clean' mode no newlines are added to the inside of data containing elements. The 'default' will continue to add a newline to the messages to keep the hysterical porpoises happy.
since_id
This parameter, which defaults to 0, is the message_id that all returned messages will be higher than. Thus it is NOT inclusive. This is to allow clients to easily only fetch new messages, and not the whole lot on every fetch. Clients can simply set the since_id to be the same value as the highest message_id they have seen from the ticker before and get only new content.
archived
This value may be 'both' in which case both archived and nonarchived messages will be returned. Otherwise any FALSE value or 'no' or omitting the parameter will result in only nonarchived messages as it was before this rollout. Any other value which perl thinks is TRUE will result in only archived messages being returned.
max_recs
This determines how many records will be returned with the fetch. It is hard limited depending on what the 'archived' parameter is. If 'archived' is TRUE then this limit is currently 100 records at a time. If 'archived' is false (meaning private messages only) it is currently set to 10_000 records at a time. This is to keep the hysterical porpoises happy, and as is stated above WILL be changed to the same hard limit as when archived messages. This change will occur no earlier than 2004-08-01. This should allow people plenty of time to convert your clients over. (All of you who have to do this should thank theorbtwo for the time given to do so as I'm a hardass when it comes to hysterical porpoises and I would have just enforced the same limit from the get-go. Incentive and all that ;-)

Additional changes have been made to the INFO tag, with several additional status attributes added to make debugging and etc. easier. Please review the ticker itself for details.

Anyway, I hope these changes are useful to you all.

sporty: we expect to see a new KB rollout using this stuff PDQ man, and don't forget the char length restiction... ;-)

Cheers,


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi


• Update:  
castaway kindly pointed out that I had misnamed since_id as from_id. I blame exhaustion, but accept full responsibility for the mistake. Please accept my apologies if this has caused anyone to waste time debugging this "error".



In reply to Y.A.N.F: Private Message XML Ticker by demerphq

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (1)
As of 2022-07-01 06:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My most frequent journeys are powered by:









    Results (98 votes). Check out past polls.

    Notices?