pandaapo commented on PR #4817: URL: https://github.com/apache/eventmesh/pull/4817#issuecomment-2041492816
> > sending prompt and getting the result of cloudevents specification from ChatGPT > > I also think it's a good idea, but it's technically unworkable. > > This is the required ChatGPT source connector architecture described in [#4047 (comment)](https://github.com/apache/eventmesh/issues/4047#issuecomment-1569754745): > >  > > If we let ChatGPT source connector to send prompts, then there will be two inputs, and there's no way to customize the content of prompts: > >  > > Moreover, the step that "creating new content **from source connector to Event Source**" goes against the design of the source connector. The source connector should only listen to the Event Source and receive new content. > > Secondly, In the case of GPT 3.5, even if the output format is specified using prompts, it is possible for it to output something like the following, which the source connector cannot pass directly without processing: > > ``` > Of course. Here is the CloudEvent data you required: > > { > ...... > } > ``` > > On the other hand, users can enter prompts even if they are not sent by the source connector. The current design does not cause the ChatGPT source connector to not support the prompts feature. > > Any new idea? ☺️ @Pil0tXia Based on the content you've written, it seems like you may not have carefully reviewed the core functionality implemented in this PR. Otherwise, according to your understanding of https://github.com/apache/eventmesh/issues/4047#issuecomment-1569754745 , you would also have raised similar questions regarding this PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
