Talk:VibratorControlProtocol

Misspellings aside, it's a moderately well thought out protocol for sending actions to a single motor vibrator over a network. -- User:Lantin

You can't go wrong with an RFC that includes comments like:

"When a prevert wants to control the vibrating device of another prevert she or he uses the VCP-client to establish a connection to the VCP-server of the desired party."

What it lacks, however, are several important features:
 * 1) Discoverability -- You must be able to discover, by asking the device (or at least the driver), the type and position of the output devices. You must be able to retreive this information without direct user intervention. (This would be typing in a code or inserting a CD with the device description file).
 * 2) Flexibility -- People are very creative - especially with regards to sex. For this reason, it pays to design a protocol that can handle having a hemaphrodite hooked up both ways. It had better be able to handle every device currently in use by someone. This means that it should handle stim, vibe, suction, pressure feedback, pulse transmission, and probably other things I haven't heard of yet. This means community buy-in, because there's no way any one of us has done it all.
 * 3) Extensibility -- We will get the flexibility part wrong. We will miss things, and the boundless creativity of horny hackers will leave us in the lurch. The protocol should be designed so that 1.1 can be compatible with 1.0 so that the new revision doesn't break your old toys. This isn't just important, it's absolutely critical.
 * 4) Simplicity -- After all that, it should be possible for someone to read the standard, take most of the defaults and have a simple device working quickly. They should be able to use an off the shelf uController from Microchip, Atmel, Zilog, Motorola or any other major vendor, and be able to hack something together in an afternoon. The protocol should take "I don't know" for an answer, and "no capabilities" for an order.

None of this is rocket science. These elements are present in POP3, IMAP4, SMTP and many other protocols. If it's written at all correctly, the widget side of the most basic implementation of the protocol should be do-able on a $0.30 10F202 - never mind monsters that sell for the princely sum of $4.75.

More on this soon at OpenDildonicsProtocol

-- User:JRicher