1
00:00:00,320 --> 00:00:05,400
And very briefly, as I promised, I want to show you what it looks like if we restart everything.
简而言之，正如我所承诺的，我想向您展示如果我们重新启动一切会是什么样子。

2
00:00:05,400 --> 00:00:11,200
And now we go through and we put all on one worker as false, what does this mean exactly?
现在我们回顾一下，我们把所有的事情都归咎于一名工人，这到底意味着什么？

3
00:00:11,520 --> 00:00:18,040
So we are going to, of course, have the same message, the same hosted, uh, the same host that we
所以我们当然会收到相同的消息，相同的托管，呃，与我们相同的主机

4
00:00:18,040 --> 00:00:20,520
start running on localhost at 551.
开始在 551 处的 localhost 上运行。

5
00:00:21,240 --> 00:00:26,840
And we use the same tools, the same instructions, we make the same agents.
我们使用相同的工具，相同的说明，我们制作相同的代理。

6
00:00:26,840 --> 00:00:30,840
Our agent code isn't touched, but now it's going to be managed differently.
我们的代理代码没有受到影响，但现在将以不同的方式进行管理。

7
00:00:31,160 --> 00:00:34,920
We're now going to run this and we're going to be following this line right here.
我们现在要运行这个，我们将在这里遵循这条线。

8
00:00:35,040 --> 00:00:42,120
And this is actually going to create three different runtimes that I'm calling worker one, worker two,
这实际上会创建三个不同的运行时，我称之为工作人员一、工作人员二，

9
00:00:42,120 --> 00:00:44,240
and worker and just worker for the third one.
第三个是工人，只是工人。

10
00:00:44,520 --> 00:00:45,640
Uh, the judges one.
呃，评委之一。

11
00:00:45,840 --> 00:00:51,360
And we're going to start each of these three, uh, gRPC worker runtimes.
我们将分别启动这三个 gRPC 工作运行时。

12
00:00:51,600 --> 00:00:57,080
And then player one, we're going to register with worker one, player two with worker two.
然后玩家一，我们将向工人一注册，玩家二向工人二注册。

13
00:00:57,320 --> 00:01:00,720
And the judge uh, with just the one that's just called worker.
还有法官，呃，只有一个叫做工人的人。

14
00:01:00,920 --> 00:01:02,360
And so that is happening.
事情就是这样发生的。

15
00:01:02,400 --> 00:01:03,480
And so what's the difference here.
那么这里有什么区别呢？

16
00:01:03,480 --> 00:01:10,610
What we're saying is that instead of having, instead of having our three agents running in a remote
我们所说的是，不要让我们的三个代理在远程运行

17
00:01:10,650 --> 00:01:18,490
worker on on our remote host, we now have three workers, and the three workers are each running one
在我们的远程主机上，我们现在有三个工作人员，并且这三个工作人员各自运行一个

18
00:01:18,490 --> 00:01:19,170
of our agents.
我们的代理商。

19
00:01:19,170 --> 00:01:21,490
So they're now in different runtimes.
所以他们现在处于不同的运行时。

20
00:01:21,490 --> 00:01:22,570
They're all on the same host.
它们都在同一主机上。

21
00:01:22,570 --> 00:01:26,210
But you could imagine that this is now they're completely separate.
但你可以想象，现在他们已经完全分开了。

22
00:01:26,250 --> 00:01:30,690
This is something where things are interacting between runtimes.
这是运行时之间交互的东西。

23
00:01:30,890 --> 00:01:34,450
And so now we send the same go message.
现在我们发送相同的 go 消息。

24
00:01:34,730 --> 00:01:39,490
And presumably very similar messages are now crossing the ether.
想必非常相似的消息现在正在传播。

25
00:01:39,730 --> 00:01:44,890
One agent is calling Gpt4 on many for the pros, one agent for the cons.
一位代理人在许多方面为赞成者打电话给 Gpt4，另一名代理人则为反对者打电话。

26
00:01:44,890 --> 00:01:50,810
And then as a result of that they will come back to the to the judge.
然后他们就会回到法官那里。

27
00:01:51,410 --> 00:01:58,210
And the judge has come I will we see pretty similar looking pros.
法官来了，我们会看到看起来非常相似的职业选手。

28
00:01:58,250 --> 00:02:00,090
The community and support is a new one.
社区和支持是一种新的。

29
00:02:00,090 --> 00:02:09,290
I think scalability is now put first the cons, um, limited customization that seems to slightly fly
我认为现在把可扩展性放在首位，嗯，有限的定制似乎有点不靠谱

30
00:02:09,290 --> 00:02:12,940
in the face of flexibility I guess our agents disagree.
面对灵活性，我想我们的代理人不同意。

31
00:02:13,300 --> 00:02:19,340
Uh, performance variability, cost considerations and ethical and content control.
呃，性能可变性、成本考虑以及道德和内容控制。

32
00:02:19,380 --> 00:02:19,780
Okay.
好的。

33
00:02:20,060 --> 00:02:24,460
Uh, but nonetheless, the recommendation is to proceed.
呃，但是尽管如此，建议还是继续。

34
00:02:24,700 --> 00:02:32,180
That is the view of even even when we distribute across multiple workers, it does still maintain that
即使我们分布在多个工人身上，它仍然坚持认为

35
00:02:32,180 --> 00:02:32,820
viewpoint.
观点。

36
00:02:33,060 --> 00:02:33,980
Uh, so there we go.
呃，我们就这样吧。

37
00:02:34,020 --> 00:02:37,620
That the example I wanted to show you, I know we've gone through it quickly, but it's just to get
我想向您展示的示例，我知道我们已经很快完成了它，但这只是为了得到

38
00:02:37,620 --> 00:02:45,300
that sense that the powerful thing about this is that without changing your, your, your code with
这种感觉的强大之处在于，无需更改您的代码

39
00:02:45,340 --> 00:02:50,900
the same definitions of your classes, these can be running in different configurations and different
类的相同定义，它们可以在不同的配置和不同的环境中运行

40
00:02:50,900 --> 00:02:52,100
kinds of runtimes.
各种运行时。

41
00:02:52,140 --> 00:02:59,700
And basically, uh, the what Autogen is doing is it's handling message calling across process boundaries
基本上，呃，Autogen 正在做的是处理跨进程边界的消息调用

42
00:02:59,740 --> 00:03:06,220
as transparently as if these were just simply classes with, with, uh, with methods calling each other
透明地就好像这些只是简单的类，具有相互调用的方法

43
00:03:06,260 --> 00:03:09,860
directly in Python code, that abstraction is what it's doing.
直接在 Python 代码中，该抽象就是它正在做的事情。

44
00:03:09,900 --> 00:03:16,060
And when you think about a future when potentially there could be, uh, millions or maybe even Billions
当你想到未来时，可能会有，呃，数百万甚至数十亿

45
00:03:16,060 --> 00:03:19,140
of agents interacting all over the place.
代理在各处进行交互。

46
00:03:19,260 --> 00:03:22,820
What Microsoft is doing is putting their stake in the ground for this.
微软正在做的就是为此投入他们的股份。

47
00:03:22,860 --> 00:03:24,820
This is a sort of playpen.
这是一种婴儿围栏。

48
00:03:24,980 --> 00:03:29,380
This is a world where agents can live and interact.
这是一个智能体可以生活和互动的世界。

49
00:03:29,580 --> 00:03:36,180
You just put your agent code within this wrapper, this agent wrapper, you make your versions of message,
你只需将你的代理代码放入这个包装器中，这个代理包装器中，你就可以制作你的消息版本，

50
00:03:36,420 --> 00:03:39,660
uh, the that that you declare the way that we have.
呃，你声明的方式就是我们所拥有的。

51
00:03:39,820 --> 00:03:44,580
And then your agents can interact with each other, no matter where they are in the world, and no matter
然后您的代理可以相互交互，无论他们在世界的哪个地方，也无论

52
00:03:44,620 --> 00:03:46,900
what programming language they're written in.
它们是用什么编程语言编写的。

53
00:03:46,940 --> 00:03:50,180
And with that, that brings us to the end of day four.
就这样，我们第四天就结束了。

54
00:03:50,220 --> 00:03:52,300
It means we're getting on to day five.
这意味着我们即将进入第五天。

55
00:03:52,460 --> 00:03:57,900
And in the spirit of the other things we've done this week, the project is going to be some something
本着我们本周所做的其他事情的精神，这个项目将会是一些东西

56
00:03:57,900 --> 00:03:59,980
that's more a sort of an idea.
这更像是一种想法。

57
00:03:59,980 --> 00:04:04,140
It's more something to tease out some thinking, to give you some some insights.
更多的是梳理一些想法，给你一些见解。

58
00:04:04,140 --> 00:04:10,220
It's not as much of a kind of commercial banger, perhaps, as the prior week, which is really great,
也许，这不像前一周那样是一种商业狂欢，这真的很棒，

59
00:04:10,220 --> 00:04:12,700
but I think it will intrigue you in new ways.
但我认为它会以新的方式引起你的兴趣。

60
00:04:12,820 --> 00:04:17,540
And a lot of what we've been doing with Autogen is about stretching what you think might be possible,
我们与 Autogen 所做的很多事情都是为了扩展你认为可能的事情，

61
00:04:17,540 --> 00:04:19,900
and that will be the plan for tomorrow.
这将是明天的计划。

62
00:04:20,060 --> 00:04:21,740
And I can't wait to show it to you.
我迫不及待地想向您展示它。