[Pidgin] #4688: Generic method to report unrecognized messages and optionally save to file for later analysis

[Pidgin]

#4688: Generic method to report unrecognized messages and optionally save to file
for later analysis
-----------------------+----------------------------------------------------
 Reporter:  jeff       |       Owner:                 
     Type:  defect     |      Status:  new            
 Priority:  minor      |   Milestone:  Patches welcome
Component:  libpurple  |     Version:  2.3.1          
 Keywords:  msimprpl   |     Pending:  0              
-----------------------+----------------------------------------------------
 It would be nice if libpurple had some mechanism for protocol plugins to
 report unrecognized packets or message types from a server. The
 information could optionally be dumped to a file, then a user could send
 the file to libpurple developers for later analysis to figure out how to
 incorporate support for the unrecognized packet into the plugin, if
 desired. This could be particularly useful in the MySpaceIM plugin, where
 a large part of the protocol is unknown.

 IServerd, at http://iserverd.khstu.ru/oscar/wanted.html , has this
 feature.

 The MySpaceIM plugin has a msim_unrecognized() function but all it does is
 log the message using purple_debug_info(). The user won't see it unless
 they have debugging enabled, and even then, it will be hidden among other
 debugging information.

 The API could be as simple as adding a new constant to `PurpleDebugLevel`,
 `PURPLE_DEBUG_UNRECOGNIZED`, and a convenience function
 `purple_debug_unrecognized` to call `purple_debug` with this constant.
 Would be up the UI to save the unrecognized log data.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/4688>
Pidgin <http://pidgin.im>
Pidgin