This is a good venue. I think XMPP and polling can be explored.
But for the needs of BlogEd [1] on which I am working, and for my
personal needs,
I would really like us to introduce an extension to the link concept,
to provide
a pointer to the next page in a historically ordered sequence of
James M Snell wrote:
If I understand Bob's solution correctly, it goes something like:
1) wake up
2) scratch whatever you need to scratch
3) turn on computer, launch feed reader
4) feed reader does some RFC3229+feed magic to catch up on what happened
during the night
5) feed reader opens a
Sam Ruby wrote:
P.S. Why is this on atom-sytax? Is there a concrete proposal we are
talking about here? Is there likely to be?
Because James Snell asked a question?.. But, more seriously:
I intend to write an Internet draft for RFC3229+feed and hope that I'll
be able to get the
Bob Wyman wrote:
Joe Gregorio wrote:
The one thing missing from the analysis is the overhead, and
practicality, of switching protocols (HTTP to XMPP).
I'm not aware of anything that might be called overhead. What our
clients do is, upon startup, connect to XMPP and request the list
Eric Scheid wrote:
how does Atom over XMPP help in this scenario:
1) wake up
2) scratch myself, stagger around in morning fog
3) turn on computer, launch feed reader
4) wonder what changes happened during the night
This is not the thread you're looking for - go back to bed!
cheers
Bill
Henry Story wrote:
[...] Something like:
link rel=http://.../next; href=http://bblfish.net/blog/archive/
2005-05-10.atom
would be really useful.
Henry,
Mark Nottingham did something on this a while back; try digging through
the archives.
cheers
Bill
On 6/18/05, Joe Gregorio [EMAIL PROTECTED] wrote:
On 6/17/05, Sam Ruby [EMAIL PROTECTED] wrote:
P.S. Why is this on atom-sytax? Is there a concrete proposal we are
talking about here? Is there likely to be?
Were you expecting [atom-syntax] to vanish in a puff of smoke
once we have a
Joe Gregorio wrote:
On 6/17/05, Sam Ruby [EMAIL PROTECTED] wrote:
P.S. Why is this on atom-sytax? Is there a concrete proposal we are
talking about here? Is there likely to be?
Were you expecting [atom-syntax] to vanish in a puff of smoke
once we have a couple RFCs under our belt? Given
At 10:06 PM -0400 6/17/05, Sam Ruby wrote:
P.S. Why is this on atom-sytax? Is there a concrete proposal we
are talking about here? Is there likely to be?
Wearing my co-chair hat:
IETF WG mailing lists are normally used for creating specs that are
listed in the charter. They are also used
On Friday, June 17, 2005, at 12:32 PM, Bob Wyman wrote:
This is *not* simpler than taking a push feed using Atom over XMPP.
For a push feed, all you do is:
1. Open a socket
2. Send a login XML Stanza
3. Process the stanzas as they arrive.
...
For your
Antone Roundy wrote:
XMPP:
5. If the feed had entries that were old and not updated, go to step 7 6.
If the feed has a first or next or whatever link, go to step 1 using
that link 7. Open a socket 8. Send login XML stanza
I am assuming that if you are pushing entries via Atom over
On 6/17/05, Bob Wyman [EMAIL PROTECTED] wrote:
Let's keep Atom as it is now -- without the first and next tags
and encourage folk who need to keep up with high volume streams to use Atom
over XMPP.
-1
Let's keep Atom as it is now explain to folks who need to keep up with
high volume
Joe Gregorio wrote:
The one thing missing from the analysis is the overhead, and
practicality, of switching protocols (HTTP to XMPP).
I'm not aware of anything that might be called overhead. What our
clients do is, upon startup, connect to XMPP and request the list of Atom
files that
On 6/17/05, Bob Wyman [EMAIL PROTECTED] wrote:
Joe Gregorio wrote:
The one thing missing from the analysis is the overhead, and
practicality, of switching protocols (HTTP to XMPP).
I'm not aware of anything that might be called overhead.
I was referring to switching both the client
On 18/6/05 6:57 AM, Bob Wyman [EMAIL PROTECTED] wrote:
Let's keep Atom as it is now -- without the first and next tags
and encourage folk who need to keep up with high volume streams to use Atom
over XMPP. Lowered bandwidth utilization, reduced latency and simplicity are
good things.
how
Joe Gregorio wrote:
On 6/17/05, Bob Wyman [EMAIL PROTECTED] wrote:
Joe Gregorio wrote:
The one thing missing from the analysis is the overhead, and
practicality, of switching protocols (HTTP to XMPP).
I'm not aware of anything that might be called overhead.
I was referring to
Sam asked
P.S. Why is this on atom-sytax? Is there a concrete proposal we are
talking about here? Is there likely to be?
I launched this discussion here for three reasons:
1. Everyone who care's about it is probably already here
2. Main discussion about the syntax is pretty much
That's what I believe Bob's RFC3229+Feed proposal addresses.
If I understand Bob's solution correctly, it goes something like:
1) wake up
2) scratch whatever you need to scratch
3) turn on computer, launch feed reader
4) feed reader does some RFC3229+feed magic to catch up on what happened
18 matches
Mail list logo
