困惑，这是poco吗？

Question

Let's say that I want to implement following interface:

public interface ICar
{
   bool IsMoving();
   bool IsRegistered();
   int CurrentSpeed {get; set;}
} 

   public class Car : ICar
   {
       public int CurrentSpeed {get; set;}        
       public bool IsMoving()
       {
         // some logic here
       }
   }

Does this IsMoving() method break poco definition?

Answer 1

POCO is a trait of framework design, which means that (some) code using the framework doesn't have to be adapted for it. Most notably, in an ORM framework, it means that the entity classes don't have to, say, implement IEntity to allow being persisted in a database.

This means that in your own code , you don't need to care about what is and isn't "POCO". However, if you require other people using your code to implement ICar , then you're not allowing them to use POCOs.

Answer 2

Check this link DTO ver POCO

POCO vs DTO

The cite (but read the link and follow other links there)

...A POCO follows the rules of OOP. It should (but doesn't have to) have state and behavior. POCO comes from POJO, coined by Martin Fowler...

Other words, it is absolutely OK, if POCO has behavior. The requirement for POCO is unaware of the persistence