hi, meng

are u talking about some entire workflow?

if so, i guess there were some slides, sorry no lucky to find it now :(.

But i did have a brief version in the attachment.

Feel free to use it.

Thanks!

On Wed, Jun 14, 2017 at 10:32 AM, meng <qsmeng@...> wrote:

Hi everyone,

  The  fabric is more complex than permissonless platforms, like Ethereum, Bitcoin.   As there is no detailed document describing the fabric, people aiming to modify fabric code has to  read the source codes. This is also difficult.

  It is better if someone could provide a document describing  in detail the data flow from one component to another component in the following procedure: client application invoke a transaction, and finally query the state after the transaction.  Here "component" refers to client application, ledger, and something like.

 Thank you.

 Best regards,

Meng

  

 

_______________________________________________
Hyperledger-fabric mailing list
Hyperledger-fabric@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric

--

Best wishes!

Baohua Yang

hi meng

For a quick answer:

1. peer node will use the ProcessProposal() method (see core/endorser/endorser.go) to handle the proposal.

2. orderer will use the Broadcast() method (see orderer/server.go) to handle the tx.

Maybe we need to add more details in the coming documentation.

Thanks!

On Wed, Jun 14, 2017 at 1:24 PM, meng <qsmeng@...> wrote:

Hi Baohua,

  Thank you very much for the dataflow. It helps me a lot.

  Further, if there exist answer to the following questions, that would be great! 

  1. APP/SDK use what api/function to form tx proposal and use what api/function to send tx proposal to peer, 

   2. peer use what api/function to receive the tx proposal and use what api/function to deal with the received tx proposal, and do what work on the proposal.

  3. similar questions for other steps.

  Maybe I expect too much.

  Thank you again.

  Best regards,

Meng.

At 2017-06-14 11:37:01, "Baohua Yang" <yangbaohua@...> wrote:

hi, meng

are u talking about some entire workflow?

if so, i guess there were some slides, sorry no lucky to find it now :(.

But i did have a brief version in the attachment.

Feel free to use it.

Thanks!

On Wed, Jun 14, 2017 at 10:32 AM, meng <qsmeng@...> wrote:

Hi everyone,

  The  fabric is more complex than permissonless platforms, like Ethereum, Bitcoin.   As there is no detailed document describing the fabric, people aiming to modify fabric code has to  read the source codes. This is also difficult.

  It is better if someone could provide a document describing  in detail the data flow from one component to another component in the following procedure: client application invoke a transaction, and finally query the state after the transaction.  Here "component" refers to client application, ledger, and something like.

 Thank you.

 Best regards,

Meng

  

 

_______________________________________________
Hyperledger-fabric mailing list
Hyperledger-fabric@...ledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric

--

Best wishes!

Baohua Yang

 

--

Best wishes!

Baohua Yang

Hi Baohua,

   Yes, that document is really needed. I am here waiting for that. 　

   I know　one　github project https://github.com/yacovm/fabricDeployment

   There should be one short chapter describing the whole dataflow with some details on main api/function used. after this it is easy to read other chapter.

   Thank you.

  Best regards,

meng

At 2017-06-14 13:46:30, "Baohua Yang" <yangbaohua@...> wrote:

hi meng

For a quick answer:

1. peer node will use the ProcessProposal() method (see core/endorser/endorser.go) to handle the proposal.

2. orderer will use the Broadcast() method (see orderer/server.go) to handle the tx.

Maybe we need to add more details in the coming documentation.

Thanks!

On Wed, Jun 14, 2017 at 1:24 PM, meng <qsmeng@...> wrote:

Hi Baohua,

  Thank you very much for the dataflow. It helps me a lot.

  Further, if there exist answer to the following questions, that would be great! 

  1. APP/SDK use what api/function to form tx proposal and use what api/function to send tx proposal to peer, 

   2. peer use what api/function to receive the tx proposal and use what api/function to deal with the received tx proposal, and do what work on the proposal.

  3. similar questions for other steps.

  Maybe I expect too much.

  Thank you again.

  Best regards,

Meng.

At 2017-06-14 11:37:01, "Baohua Yang" <yangbaohua@...> wrote:

hi, meng

are u talking about some entire workflow?

if so, i guess there were some slides, sorry no lucky to find it now :(.

But i did have a brief version in the attachment.

Feel free to use it.

Thanks!

On Wed, Jun 14, 2017 at 10:32 AM, meng <qsmeng@...> wrote:

Hi everyone,

  The  fabric is more complex than permissonless platforms, like Ethereum, Bitcoin.   As there is no detailed document describing the fabric, people aiming to modify fabric code has to  read the source codes. This is also difficult.

  It is better if someone could provide a document describing  in detail the data flow from one component to another component in the following procedure: client application invoke a transaction, and finally query the state after the transaction.  Here "component" refers to client application, ledger, and something like.

 Thank you.

 Best regards,

Meng

  

 

_______________________________________________
Hyperledger-fabric mailing list
Hyperledger-fabric@...ledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric

--

Best wishes!

Baohua Yang

 

--

Best wishes!

Baohua Yang