U++ framework: U++ Core » pimp Stream for protocol generation/processing

Home » U++ Library support » U++ Core » pimp Stream for protocol generation/processing

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

pimp Stream for protocol generation/processing [message #35630]

Thu, 08 March 2012 10:50

kohait00
Messages: 939
Registered: July 2009
Location: Germany

Experienced Contributor

hi there

Stream is quite a usefull thing. could be used to actually serialize/deserialize custom communication protocols. but it has no very slim virtual interface only. it's be great to be able to override them, to realize custom serialisation/deserialization.

any comments? should i provide a draft/patch?

Report message to a moderator

Re: pimp Stream for protocol generation/processing [message #35640 is a reply to message #35630]

Fri, 09 March 2012 11:58

mirek
Messages: 14290
Registered: November 2005

Ultimate Member

kohait00 wrote on Thu, 08 March 2012 04:50

but it has no very slim virtual interface only.

Sorry, I do not understand what this is supposed to mean...

BTW, any changes to Stream should take into account that we need Put and Get definitions to be exactly as they are, for performance reasons...

Mirek

Report message to a moderator

Re: pimp Stream for protocol generation/processing [message #35646 is a reply to message #35640]

Fri, 09 March 2012 18:31

kohait00
Messages: 939
Registered: July 2009
Location: Germany

Experienced Contributor

ofcorse...

i didnt mean to change those..

slim interface means, that the GetPut's are not virtual. thus not overrideable..

stream has a lot of potential for protocol handling, not only as a data connection point. but it should be esier customizable..

Report message to a moderator

Re: pimp Stream for protocol generation/processing [message #35647 is a reply to message #35646]

Fri, 09 March 2012 18:43

mirek
Messages: 14290
Registered: November 2005

Ultimate Member

kohait00 wrote on Fri, 09 March 2012 12:31

ofcorse...

i didnt mean to change those..

slim interface means, that the GetPut's are not virtual. thus not overrideable..

But that is the point. Basic Get Put cannot be virtual, because we want it inlined. Otherwise our performance would be subpar..

Mirek

Report message to a moderator

Previous Topic:	NetNode Win32 code addition
Next Topic:	RectTracker : usage of the callback sync

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 27 19:26:13 GMT+2 2026

Total time taken to generate the page: 0.00818 seconds