[This message was posted by FPL  Program Office of FIX Protocol Ltd. 
<f...@fixprotocol.org> to the "Website Feedback" discussion forum at 
http://fixprotocol.org/discuss/38. You can reply to it on-line at 
http://fixprotocol.org/discuss/read/b3e25722 - PLEASE DO NOT REPLY BY MAIL.]

Just a quick note that this has been added to the Jira issue tracking system.



> This sounds like a bug of the FPL website. I have not experienced
> delayed or retransmitted postings but you should alert this forum to
> such behavior. I don't think it is intentional to retransmit old
> messages. Maybe others had similar experiences and can comment here.
> 
> The aspect of new postings to old topics is interesting as it could be
> valuable to scan recent postings on a forum one is not subscribed to.
> That is only possible by doing a "Show All" and looking for red font. It
> would be nice to have the ability to collapse or expand individual or
> all entries and see the entry time as well as the latest update time on
> the line of a collapsed item.
> 
> For now, subscribing to forums and following the direct link to a new
> comment for an old posting is the only way I am aware of but it is good
> enough for me.
> 
> > I did not "retransmit" old messages, they "got" retransmitted -
> > softwares are not perfect and
> > http://en.wikipedia.org/wiki/Software_bug states "it is often
> > considered impossible to write completely bug-free software of any
> > real complexity".
> >
> > If my final device has not received a posting and if its not visible
> > in the discussion forum, then the posting is not visible to me and I
> > have no other way of knowing a message has been posted, so the post
> > gets ignored though not by choice.
> >
> > I use two methods of viewing latest activity on the FIXProtocol.org
> > discussion forums :-
> >
> > 1) Receive email subscriptions
> >
> > 2)Visit http://fixprotocol.org/discuss/ to see latest postings. If a
> >   forum indicates a new post has been made with "Last updated DD MMM
> >   CCYY HH:MM XM" with the date time part in Red color, I open that
> >   forum to see latest activity. The problem here is topics with new
> >   replies do not "bubble up" like they do in many discussion forums,
> >   for example http://www.coderanch.com/forums/f-25/Developer-Certification-
> >   SCJD and other forums at the coderanch site. This was a feature
> >   request suggested in http://fixprotocol.org/discuss/read/ac424324
> >   and http://fixprotocol.org/discuss/read/1eda1833
> >
> > From the message contents (not header) I want to be able to do a
> > staleness check because [Start quote from 
> > http://www.ez2ba.com/html/help/guides/viewing-email-
> > headers.html ] Many email programs hide much of the header information
> > because most of the time you don't need it.[End quote] Posting date &
> > time in email body is to help discard old messages. As an example
> > below is the "Full Headers" from a Yahoo email that I received from
> > Implementation and Optimization working group
> >
> > [Start "Full headers" from Yahoo email]
> >
> > FPL Implementation & Optimization Working Group Tuesday, July 21, 2009
> > 2:03 PM From FPL Meeting Tue Jul 21 11:03:08 2009 Return-Path:
> >   <ical_instance+5344_7...@fixprotocol.org> Authentication-Results:
> >   mta503.mail.mud.yahoo.com from=fixprotocol.org; domainkeys=neutral
> >   (no sig) Received: from 198.104.138.17 (EHLO mail.angel.net)
> > (198.104.138.17) by mta503.mail.mud.yahoo.com with SMTP; Tue, 21 Jul
> >                  2009 11:03:10 -0700 Received: from
> >                  localhost.localdomain (va4.angel.net
> > [216.167.119.55]) by mail.angel.net (Postfix) with ESMTP id
> >                 604E461404A for <kay_mah...@yahoo.com>; Tue, 21 Jul
> >                 2009 14:03:08 -0400 (EDT) Content- Type:
> >                 multipart/mixed; boundary="----------=_1248199388-11181-
> >                 40" Content-Transfer- Encoding: binary MIME-Version:
> >                 1.0 From: FPL Meeting
> >                 <ical_instance+5344_7...@fixprotocol.org> Add sender
> >                 to Contacts Subject: FPL Implementation & Optimization
> >                 Working Group To: kay_mah...@yahoo.com Message-Id:
> >                 <20090721180308.604e4614...@mail.angel.net> Date: Tue,
> >                 21 Jul 2009
> > 14:03:08 -0400 (EDT) Content-Length: 12399 Message contains
> >       attachments instance_7121.vcs (2KB)
> >
> > [End "Full headers" from Yahoo email]
> >
> > Note that there is no Sent time / date only a received date and time.
> >
> > I am not talking of the date of the original posting in replies, I am
> > only recommending including the date and time of current post in the
> > email subscription - either a reply or creation of new thread. I agree
> > interest is triggered by topic and not by posting date.
> >
> > I thought adding date and time in email body is an easy task which
> > could help many people who are reading email subscriptions.
> >
> > > This sounds like a very special case where you retransmit email
> > > messages to a forwarded location with one month delay. Does this
> > > mean that you would ignore postings that your final device has not
> > > received within a certain time frame?
> > >
> > > The normal case would be that the email is sent to you within
> > > minutes from being posted. I think that is sufficient. The email-
> > > header contains the SendingTime, it is the envelope for the posting.
> > > The date of the original posting might be more interesting to see if
> > > someone responded to an older post. Still, my interest is triggered
> > > by the topic and not by the posting date.
> > >


[You can unsubscribe from this discussion group by sending a message to 
mailto:unsubscribe+100932...@fixprotocol.org]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to FIX-Protocol@googlegroups.com
To unsubscribe from this group, send email to 
fix-protocol+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/FIX-Protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to