0000401: more control over discarded output

ID	Project	Category	View Status	Date Submitted	Last Update

0000401	LDMud 3.3	Networking	public	2005-09-09 06:58	2010-08-18 14:55

Reporter	lynx	Assigned To	Gnomi
Priority	normal	Severity	feature	Reproducibility	always
Status	resolved	Resolution	duplicate
Product Version	3.3
Fixed in Version	3.3.719

Summary	0000401: more control over discarded output
Description	this is how comm.c:add_message() handles the case of output lost in transmission as reported by a EINTR or EWOULDBLOCK. additionally we get some stderr warnings. if (ip->msg_discarded) { ip->msg_discarded = MY_FALSE; add_message("%s", "\n* Text lost in transmission \n"); / msg_discarded might be TRUE again now */ } i would prefer it the interactive or at least the master object was called instead, and given as much information as possible on the event. then it can decide to either recover the network link, or to drop it. but having a string output which is meaningless to most protocols other than telnet, is not exactly the solution these days... :-/
Tags	No tags attached.

Date Modified	Username	Field	Change
2005-09-09 06:58	lynx	New Issue
2009-01-05 03:44	Gnomi	Relationship added	child of 0000297
2009-05-19 16:04	Gnomi	Note Added: 0001121
2009-05-19 16:04	Gnomi	Relationship replaced	duplicate of 0000297
2009-05-19 16:04	Gnomi	Duplicate ID	0 => 297
2009-05-19 16:04	Gnomi	Status	new => resolved
2009-05-19 16:04	Gnomi	Fixed in Version	=> 3.3.719
2009-05-19 16:04	Gnomi	Resolution	open => duplicate
2009-05-19 16:04	Gnomi	Assigned To	=> Gnomi
2010-08-18 14:55	zesstra	Note Added: 0001898

Gnomi 2009-05-19 16:04 manager ~0001121	In r2551 a driver hook was implemented, that is called after messages had to be discarded.

zesstra 2010-08-18 14:55 administrator ~0001898	I haven't noticed it since then, but I did not use Mantis much, because vacations and not enough time.