Parent Directory | Revision Log
Links to HEAD: | (view) (annotate) |
Sticky Revision: |
use local configuration if available
correct trunk
1 Fixed: Added SIGPIPE handler. We noticed that under heavy load Meteor receives SIGPIPEs from the OS, suspected to relate to clients that have just disconnected the moment Meteor attempts to write to the socket. This caused Meteor to crash. 2 Fixed: Long polling multiple channels no longer causes the loop to die and restart when some channels have messages queued for delivery. 3 Fixed: Over time, Meteor 'collected' connections from clients that never got disconnected even if MaxTime was set. This happened if the client concerned sent a header with no terminating blank line. Meteor kept waiting for the rest of the header, which never arrived, and therefore the client remained in limbo, never subjected to the MaxTime time limit because it had not yet become a subscriber. Clients are now allowed 30 seconds to send a valid request header. 4 Fixed: If only one message existed on the server, the JS client would continue to request it again and again, because it has message ID 0, and the JS client considered this an invalid message ID. 5 Fixed: Corrected some comments in file headers 6 Changed: MaxMessages has been renamed to CloseOnEvent and functions in a similar, but not quite identical way. Thanks to Matthew Haak, who pointed out the extreme confusingness of MaxMessages and a bug that has resulted in Fix 2 above. Setting CloseOnEvent to any value that evaluates to true will cause Meteor to close subscriber connections after at least one message has been sent and there are no further messages pending. This is identical to MaxMessages for values of 0 and 1, but where MaxMessages is set to a value higher than one, replacing it with CloseOnEvent with the same value will act as though it were set to one. The intent of MaxMessages was to enable long- polling (and it is used by the JS client in that way), and CloseonEvent is a drop in replacement for that behaviour. 7 Changed: Meteor JS client now uses dynamic <SCRIPT> tags for all polling behaviours, rather than XHR. This enables it to make poll requests cross-domain (see 13) 8 Changed: Meteor JS client now abstracts timestamp lookups to a dedicated method. 9 Changed: Default HeaderTemplates no longer include cache busting headers, since all meteor requests contain a millisecond timestamp and so no client makes the same request twice. These were therefore simply chewing up bandwidth. 10 Changed: Date strings used for logging debug messages are cached to avoid numerous expensive lookups to localtime(). 11 Changed: Channel info is only sent in a response if the client does not request a restart from a specified ID. The logic being that if the client knows the ID they want to start from, they have already made previous requests and have the channel information they need. Bandwidth saving measure. 12 Added: JS client now has a Meteor.isSupportedBrowser() method, which you can call to detemine whether Meteor will run in the user's browser version. 13 Added: JS client can now use different hosts for polling and streaming. This is only really useful if your website is on a domain that has a lot of cookies, and you don't want to send them in every poll request. Removing cookies from request headers can reduce the size of the request significantly. We find that with cookies included Meteor poll requests are usually larger than the responses. To use, set Meteor.pollhost. Meteor.pollhost can be any domain, while Meteor.host must be a subdomain of your website hostname. 14 Added: Config file now supports new 'FooterTemplate' parameter, for a string to send just before the connection to the subscriber is closed. This is in support of change 7. 15 Added: Better inline documentation for ChannelInfoTemplate config parameter 16 Added: Log output includes connection IDs corresponding to the file inode for each connection 17 Added: New controller command LISTCONNECTIONS, produces a newline delimited list of all currently connected clients, and for each one displaying "ConnectionID IPAddress ClientType [SubscriberID]" 18 Added: New controller command DESCRIBE, takes a ConnectionID as a parameter, and outputs numerous statistics about that particular client, including number of messages sent/received, user agent, IP address, time connected, time remaining until MaxTime etc. 19 Added: New controller comment LISTSUBSCRIBERS, produces a newline delimited list of all currently connected streaming subscribers, and for each one displaying "SubscriberID IPAddress Starttime TimeLimit TimeRemaining MessageCount UserAgent" 20 Added: SHOWSTATS command produces the following additional stats: connection_count: total current connections, real_subscribers: total of number of currently connected streaming subscribers plus the number of unique polling connections seen in the last 60 seconds. 21 Added: STDERR outputs prior to every exit() for debugging purposes 22 Added: The UDP server is now considered stable, and is the best way of broadcasting messages to lots of Meteor nodes simultaneously and efficiently.
Updated some config defaults Release
Updated default config file Updated some config narrative Channel names made more lenient
Added crossdomain.xml for flash clients Incremented version number Moved 'new message' debug notice to more useful location Moved default for ChannelInfoTemplate to correct position alphabetically in code Set simpler default HeaderTemplate Added LogTimeFormat Updated description of PingInterval, Persist Corrected misspelling of Parameter Reformatted debug output for config initialisation Added recognition of null byte in config Fixed problem with mode recognition Fixed resuming from given message ID Fixed sending of message backlog Fixed Shlemiels Logged connection duration on leavechannel Fixed name support in channelinfotemplate Added logging of reasons for connection closes Abbreviated log output Fixed tracking of subscriber IDs Added logging of user agent Fixed incorrect key for MessageTemplate in Subscriber.pm Add some additional code comments Fixed incorrect closure of new connection if previous connection close was waiting on write buffer
• Removed support for numbered header templates and hard coded persist values, use new mode support instead
• Added simple UDP broadcast abilities
• The ADDMESSAGE response now follows the `OK` with a tab character and the message ID for the newly added message
• Mode-specific configurations • New ~channelinfo~ header keyword • New ChannelInfoTemplate parameter
• meteord will return it's version number and exit if any command line parameter is '-v', '-version' or anything in between
Complete rewrite of the JS web client Opera and Safari compatibility Saner request format
Resynced meteor.js defaults with documented values. Removed wierdness in Meteor.js subsurl Updated defaults in Config.
Attemps to prevent polling connections sending undefined requests
Updated defaults and docs, removed redundant line in meteor.js
• Change CRLF line endings back to LF only
Initial import
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
ViewVC Help | |
Powered by ViewVC 1.1.26 |