ProtoWrap is highly vulnerable to suffering DoS attacks, given the amount of processing that can be dedicated to each line. Each systems administrator must weigh what is more important to his site's operation --High availability or high security. Most systems administrators will choose security.
As ProtoWrap is built centered on security and RFC adherence and not on supporting extensions to the protocols, the extensions will be treated as erroneous commands and discarded. This might make some client-server interactions slower and some operations impossible, but --once again-- this is a compromise that many system administrators will be willing to take.
In its current status, ProtoWrap is not easy to set up. Anyone interested in running ProtoWrap must craft their own startup script. In order to allow systems administrators without Perl knowledge to set it up, a startup script reading a configuration file is among the top priorities for future development.
Due to its licensing, the code to ProtoWrap can not be included in propietary products -- If ProtoWrap is enhanced or included in another product, the changes or the product will be made available under the GPL license.