By Peter Dimov (1. October 2006, 15:50:48)
Improving some packet and class names
 (2 )

Hello everybody,

I’d like to change the names of some packets and would like to get some feedback.

Sebastien pointed out previously that Networks::Http does not make much sense since HTTP is an application layer protocol. He is absolutely right of course. Actually all that is implemented in Networks is protocols, so I’d suggest that Networks be renamed to Protocols. Gnutella and Http should be moved under Protocols some time soon.

I was thinking about this PacketParser class (see the post about packet parsing improvements) and a better name would be BinaryReader, I think. The counter piece would be BinaryWriter. I plan to put them in Utils::Encodings, which by the way should probably better be named Utils::Codes because encoding implies only one direction of code conversion and we actually implement both.

Comments?

Peter

Would you like to post a relpy?


This post starts a thread.
Follow-ups:
By Slavcho Mavrodiev (1. October 2006, 17:52:39)
Re: Improving some packet and class names
 (1)
Hi everyone, First of all to the people who don't know me, I'm one of the guys that together with Peter started the Calitko project. Unfortunately there were a lot of (more...)