Connector best practices for api

Suite and Optimus Suite 5
#1

Like what I see in the toolkit, but I don’t do anything but golang api dev. If you guys from your experience writing the connectors could come up with a tips/best practices guide on what use cases need to be covered for the server side beyond simple stateless ajax calls, that would be great.

I can cobble up basic use cases for say, various crud strategies for updating a grid, but I’d just like to know what you guys learned in the discovery process.

#2

In addition to the normal CRUD, DHX components has few extra scenarios, for specific components

  • loading the specified range of records ( for dynamic loading, the range may be defined by an index or by a parent id )
  • loading data that matches some criteria ( combo and client side filtering )

That probably will cover most use-cases