 I've heard the boss on slack earlier or a seaman, so I'm sure he's just late Hey guys, I'm gonna suck we missed you Hey Clemens It's rough when you're just front going from meeting and meeting and meeting and you actually are running them You know, it's you can't just walk away Slinky developer, that's francesco. Is that right? Yeah, it's me. Yeah, cool. I got that right I probably misspelled it, but I got it right in my head anyway. I'm gonna suck Think that's the right one I apologize. I don't have an external monitor today. So I won't be able to watch the chat as closely as I normally do All right. Hi Heinz Hello Hello, and christian are you there? Yep Hello scott There you go. Tommy, where's your message? I don't see it in zoom yet in the chat And let's see who else. Vlad, are you there? Hello and ginger Uh, good morning, Doug. Good morning. Um, hold on a couple of the people that joined Hey, Tommy, um Let's see Mike. Are you there? Yeah, I'm here. Excellent. Um There's somebody else. Vinay I apologize if I'm butchering that Yes, I'm here. Sorry. I was just gonna say this is my first meeting. Thank you for having me. No, thank you for joining. Um What company are you with by the way? I'm with Palo Alto Networks And then the yeah, okay I'm happy to do an introduction at some point if that's helpful Now we don't get that formal here just The only reason I was asking was because we keep attendance and it's usually based upon company So I just like to keep track of that But thank you for joining It actually might be a really short call today I'm sure everybody'd be very upset by that Hey, Eric. Eric, are you there? Sorry. Hey, there we go. How's it going? Uh, that's not I'm having a great morning Thank you Cool. Hey, Ryan Hello Hey, all right. Give it another minute. The one that started. All right, so it's three after the one we go I think it started And let's see You guys can't see my window, right? Yes. No, we can't see it. Okay. Cool. Okay. Cool. Just want to make sure All right, uh Nothing new with AI as I believe community time. Okay. Anything from the community that people want to bring up? That's not on the agenda All right, cool. All right. Kupkan to you Um, first of all, I don't know if anybody's been paying attention, but last I heard the Conference organizers will are still planning on having the conference despite the the virus and all the other stuff running around um So it is still on as far as I know um So some local color Say that again To have some local color on this Sure, go for it So I live very close to the Dutch border and we have a there's a My neighbor in district Is the one that is currently causing all the noise For uh for Germany and is right by the Dutch border So it's I don't want to make you anybody panicky, but it's it's like it's not so unlikely That this is going to jump into the Netherlands and it's also going to jump into into my district and then who got God, who knows what's going to happen then in terms of just you know panic reaction of Of the official so I'm currently 50 50 of this happening It's going to be interesting to see how it all plays out that is definitely for sure All right, no shaking hands with anybody You know, it's funny I was at a conference earlier this week up in new york and that's one of the first thing that ran through my mind was You know, how do I politely say sorry? I'm not going to shake your hand and unfortunately I gave into it It actually did shake two people's hands, but We'll say It's hard not to but I will say for um our project Excuse me. We do project booths. I always Put hand sanitizer at our booth So everybody can use it. I don't care if you're a you know visitor or if you're a you know Maintainer, but I always have hand sanitizer at the booth. Probably a good idea. Yep Go ahead. Sorry the elbow bump Well, I was thinking fist bump, but yeah, I like elbow bumps because usually you have some clothing that you know Exactly Although Okay, we're really digressing here, but now I'm starting to think of the Foggy horror picture show, but maybe that's going way too far. So never mind. Um, okay But speaking of booths We did get confirmation that we have a booth reserved for us. It's booth 11 If you click on that link, you can actually see more information about what the other booths are doing if you're interested Um, we are in the afternoon sessions for all three days So please if you are able to sign up for some booth times by putting your name in here I did add when the two sessions are just so you guys have that for easy reference in case you're planning on Speaking one of those or joining one of those. So for example, I think scott's no I think it's scott's session on wednesday might require several people because It's a more of a lab kind of thing and he wants people to help out there. So Think about that as you go forward. But anyway, please add your names when you get a chance Also, when you're talking about the booth, this is the text that they gave me The most interesting thing here is to make sure that you do not talk about products there That's a I think that's an obvious thing. You should talk about the technology and the spec itself But if would the interesting thing to me was This little bit right here where they said, you know, if they hear you're doing a sales pitch You know, they write they deserve the right to kick you out Which I thought was kind of interesting which makes sense, but it doesn't seem kind of brutal So keep that in mind if you are signing it for booth duty Okay Um, I think I'm trying to think of anything else here No, I think everything else is old news. So any other questions or comments relative to kubkan Can you share this document? Oh, yes. I'm sorry. Yes. That's what noise. Thank you. Yeah There is the link right there Can I just make a quick comment? Yes So hello, I'm Jonathan. So people call me Jojo and I'm very interested in serverless like open source serverless platforms And I'd like to my first meeting of the working group for serverless. So just introducing myself for the first time here I'm going to be at kubkan. I'm going to be speaking at the rejects about open source serverless as well So I just want to join What's happening on the cncf serverless working group? Great. Hi Hi and welcome. Glad you can join us. I think you're the other person now. Vinay was as new as here as well today So we've got two newcomers, which is that oh, actually there's a third person I guess you are you Would you like to introduce yourself since we're in that mode right now? Isaru Hi guys. Yeah, actually, I'm uh, just interested about this community. So just thought of coming and see So this is my first visit here Hey, oh, welcome If you can do me a favor and just put your full name and your company name If you want to be associated with the company into the zoom chat and that that way I can add it to the attendee list And we and we do track these things for for voting rights and stuff like that Okay, okay. Thank you Um, all right, hold on Geez So don't forget. All right Okay, moving forward kukam are done with. Um, okay stk call So We did not have a call last week or the week before so I don't think there's anything to mention Other than I did create the rust repo and the folks Um are currently working on doing that merging Of those two rust projects that are out there today Um, I'm assuming even though we didn't take an official vote Is there any objection to us? Pulling them in as a as a new stk repo Okay, I didn't think so because no one raised an objection before but I know we didn't do it a formal vote So just want to make that official. Uh, we do technically or I'm sorry. We are supposed to have a call today So immediately after this call, we'll have the stk call Um, unfortunately if the call Runs past the top of the hour. I will not be able to join it. So someone else will have to be Notetaker at that point just a warning for a quick call Uh, let's see. Kathy is not on the call. I believe do we have anybody else from the work flow Subgroup who wants to give status. I don't see anybody Okay Um, moving forward then let's talk about discover apis. So Clemens let me pick on you to go first since I think you said you need to leave her a little bit early Maybe you can bring us up to date on anything that might have happened. You know, I think you're on vacation Um, yes, so we've had two things that we added clouds, uh, some homework, um, and Hang on, let me see Yeah, we're doing me to scroll to and calling calling this more go a little bit further down To the sections where we have the configurations for the transports A little bit further there Oh this section okay Yeah, so, um calling added Further information we need for gnats So that's the this the subject name the cause modes pull mode Whether it's pull push and then the acknowledgement mode, which are all client-side configurable settings Um, that kind of echoes similar settings that we have lately infinity And then for mqp we, um Clouds contributed that we then talked about that in some a little bit more detail um, and We're fairly happy with that set and then we also added the htp Things which are all and all of these are effectively transport specific configuration parameters for Pushing out so you'd have a subscription manager subscription manager is tasked with taking an event and moving that elsewhere Um push and so that these are the parameters for the respective transports that we have in cloud events Um as standard transport, so we're going to go and configure those And of course every implementation if that wants to support a preparatory protocol Um can add their own as much as you can add your own transport bindings To cloud event in a preparatory fashion if you wanted to so those are the ones the protocols that we have in the In the set so that that's what that is um, and then ryan had A proposal that he has not put into this document yet, but that's the plan for filtering And we've and he's got some some variations of this ryan Are you on? I am yes Do you want do you want to show that doc? um Coincidentally, I was my laptop was forced into an update right before this meeting so I'm on my phone right now so But I do plan to uh, I do plan to put it in the doc. Um either today or tomorrow. Um, and we can cover Okay, so I will I will just I will just talk about it briefly um So we have we we thought about what what an initial filter and so this filter is really for Let's back out once. Um, also because I wrote email to Heinz earlier And he had a lengthy lengthy email to me um, but just to reiterate The difference we make here between push and pull is really These pulse pulse out subscriptions are meant to be using the capabilities of whatever broker you already have So, you know, if you're using mqp, you go and create a subscription Of sorts and then pull data towards you with mqtt. You have a subscribe gesture And again, you pulled events towards you on that same connections. That's what the pull means And of course if you're choosing mqtt, there's a certain set of filtering capabilities that exists in that broker And if you use mqp, then there's a certain set of filtering capabilities that exist in that broker May they be standardized or may they be custom? And so we're not going to touch those and and it's really like if you use any of that sort of infrastructure You're effectively compliant with this subscription model because you're using native capabilities of a broker and I don't think we need to go and and Start standardizing into mqp and we don't need to start standardizing into mqtt Because people who are using the sorts of brokers Know what they're doing Now what what's different is is if we create relationships that kind of have these multi hop deliveries where you might you might want to get You might want to deliver to mqtt clients Which needs to pull from an mqtt broker, but somehow you need to get that event into that mqtt broker And that is the sort of subscription That we're covering here. So you're creating a A routes a push route effectively from subscription manager Into that mqtt broker the event that gets delivered into the mqtt broker And then the mqtt clients basically use mqtt ways of getting of getting to that So so the filter definitions that we make here are really for only for that push delivery path and for Allowing the subscription manager to decide which which events that it gets Are eligible for delivery on a particular subscription. So that's what that's for and the minimal filter That we're defining per right as proposal is one where we have um an and combination of subject source um and type And you can match against against those values either with suffix or with prefix or with an exact match And those three Elements are combined with and And and the fact you can only use three is that it's it's it's somewhat nonsensical to have the same condition For the same field twice in an and combination because that will likely not not work You could arguably do a prefix and a suffix filter for The subject field that's that's possible Um, but that's the simplest set. So that's the simplest filter basically just anchors on those three fields And then so that's the basic. That's what we call the simple dialect and then we will have extended dialects Or we're proposing that that might be extended dialects, which then also allow You know matching against arbitrary other properties but Based on implementation experience that we have and then also that ryan has said They have um because of cost of of this matching We want to keep the simplest filter really simple and and super constrained um, and that's the thing that everybody Must implement effectively to be compliant and then we'll leave effectively the definition of further dialects to Extensions similar to the way how we've done extensions for For cloud events per se. So if someone wants to once to come and say We're we're gonna we're gonna Define a sequel dialect to match cloud events That's great And the way this and the way this ought to show up How the the filter dialects are being communicated is that in the we're assuming that in the discovery api There will be at where the subscription managers or the subscription points are being listed Um that there is already a metadata indication that says here the filters that are supported So there's that there's effectively capability negotiation Happening where where you must find you must support simple But then you can also if there was a dialect that was called sequel um that you can then already see From the the discovery metadata Um that the sequel that dialect was supported and that you can then go and instantly create a sequel filtered condition and And walk up to the subscription endpoint and that will then be accepted That's the that's the idea we have about this multiple dialects And there's some negotiation happening through ways of discovery and we might have a discovery mechanism for hdp As well, we haven't thought about how this looks in hdp just yet I'm at the protocol level, but I can imagine that we're going to have a Potentially an options extension Where you can basically walk up to the subscription manager endpoint do an options request and then you get a header with all the supported dialects For for subscriptions, which is similar to how mpp for instance would do it That's what we had. That's what we are so far in terms of of getting to a complete draft Um, I think this section is relatively good in shape. I don't I don't know how Doug what's your idea for how the I mean, they're stopped missing, but Did you think we should need to break this out into a separate document? Do we leave that section in that document? How do you think we should do this? I don't have an opinion yet about separate documents Oh, there's a dot echo um I might might be you promise if you can meet while i'm talking Okay, sorry It's my Okay, yeah, that's better. Thank you. I don't care necessarily about separate documents yet. I guess what i'm more looking for is To make sure that the text in here is more speckish, right? So for example this section right here Well, I understand The the most critical thing is to just get the information that you or get the bits that you want to have specified um, but putting that into specky language So it's more readable. I think Um, is really what i'm looking for more than anything else that way someone can we can hand this to somebody and say hey Here's a rough draft You know start commenting on it as opposed to you know when I look at this section right now Then you look at this and it's not gotta be a hundred percent sure what they're supposed to do with these things That's that's that's what i'm worried about. Yeah, so I think we need to do a solid edit pass Um on this and there's also kind of a bunch of comments on the side of this. Yes um So do we think this should should go as a we should turn this into into markup and put that into the repo I'd like to but I'd like it's up to you guys when we do it I was assuming that we'd do it when you felt like you were past the stage of sort of like daily edits um, and it and Because the minute you put it into the repo then we have to go to a pr process right or something like that Which is going to slow things down immensely um So it's kind of up to you guys No, that's fine. Um, uh, let's let's so ryan is going to put the filter section in um, and then we'll um We'll talk on tuesday what we think what the editing process will will be and then At least we have a roadmap for for how we're going to land there Because because like I could now say i'm going to take the pen i'm going to do it But um, we should go and decide that as a group and then probably also split up the work And also figure out how we're going to do and do the the mutual review Um, and we also I think we need to take the take the text out of this document because it's a little unwieldy to have You approve every single edit Yeah, and I apologize for not being on it. I've been very very busy in traveling Yeah, but that that's okay Well, we we basically need to go and go take the text we need to take the text out and make two I moved that to a different doc. So I'll I'll take that we'll we'll do that. Um, we'll talk about that on tuesday, okay All right any questions for clements or that sub team I'm still concerned about uh having suffix filtering be a requirement by default I'm fine with that being optional, but I just worry about the implementation costs Um Are you worried about prefix? No prefix is much more efficient to implement Yeah, I think what we One of the the key use cases for that is if you are doing something that is like like files Um, and you want to grab um the the file type by extension, which is fairly common Um, then you need a suffix Yeah, I'm not I'm not questioning utility. I'm just implementation costs forcing everybody to have that in And has a cost associated and we should be aware of it if we're asking people Yeah, that's that's what we're already trying to constrain this to three there's three elements but Yeah, we we we can still go and discuss that I'm I'm not I don't think we're we're we're final on this We it might be that the simplest thing that we're going to do is an exact match All right, cool. Any other questions comments? Okay, cool. Thank you Clemens I will have to excuse myself for the rest of the call. Apologize to your wife for us. Yes. Yes. Yes. Yes. Thank you All right, Mike You're up anything you want to discuss and I know you're on vacation is well unfortunate. I was also on vacation and uh Came back to a pile of work, but I wasn't expecting so Um, I'm I'm gonna need another week to get the discovery um into a more First drafty kind of states Um, if you have any I just couple of people added comments to the dock where I was gone It's great. If anybody wants to actively participate reach out to me on slack or speak up now Otherwise, I will probably draft this Either later today or tomorrow and send it out. Uh, I'll post it in this like channel when it's ready Okay, any questions or comments from Mike? All right, cool and welcome back. I hope you had fun Yeah, um, hey Doug. Sorry, this is Brian. I was just needed. Um, go ahead, Ryan Uh, so so there is some alignment. They need needs to happen between the two the subscriptions section around how filters are advertised Uh, and how, uh, that negotiation happens with discovery So, I don't know. I'm happy to to join for a session there to talk about it or Um, maybe we can just revisit it once we get this in better shape and come back as a larger group. What are your thoughts? Mike, any thoughts on that? Um, I mean, I can certainly base discovery off of what I see here in subscriptions Do you think that's a good starting point? Sure. Yeah, if you're comfortable doing that, um, uh, or if you know, you want one of us to join Just let us know Okay Okay, cool. Thanks guys Anything else relative to the new spec before we move on to the agenda? All right. Thank you everybody. Um, okay So a couple prs relative to cloud events Um, I don't know the status of this one. I know it was recently updated. Let me just double check here So Klaus you've actually taken a look at this one Actually, I'm sorry. We talked about this. I think, um On last week's sorry. I'm sorry the last phone call we had and for the most part it looked okay But then jim had a comment and the author Did update the spec or his changes based upon that comment I think he just moved things around slightly or changed some url But then klaus you actually took a look at it I just everything okay at this single attribute here the about the content coding because that was about a remark I did in another issue in the discussion um, I mean jason schema allows to to uh, specify the encoding and for a data base 64 It was clear that it is base 64 encoded. So that was my remark to add that Okay, and I assume you did that to your satisfaction, which is why I did lgtm, right? Yes, so I didn't review closely the whole structure of the jason schema which just that this single field was added right, okay Does anybody I just want to check something here. So that last little change or was done I don't know if it was done two days. Yeah, he did it two days ago, which is definitely within the time limit Does anybody need more time to look over this pr? If anybody does not feel comfortable approving it speak up and we'll let it go another week But otherwise it's been out there for a little while. So I'd like to approve it if everybody's okay with that Any objections or approving? Okay, cool. We'll do that. Thank everybody All right, I can't remember the status of this one. Unfortunately. Hold on a second Oh, yeah, okay. I did approve this one. So this one um So the distributed tracing apparently has a rule that's has our sorry Yeah, it has a rule that limits the character set of what you can use for these values and Equals is not part of that value set when I looked at the documentation um, so it seemed completely right to me But does anybody else have a chance to take a look at it or disagree with this? Just so you know, the reason you can't use commas or equals I think is because They're sort of like reserve characters because I think this is basically a comma separated list of things So therefore obviously a comma. You don't know whether it's part of the value or a separator And then equals because it's part of the you know name value pair equal thing I think that's why they made that rule Any comments on this or objection to approving? All right. Thank you I believe that is it for the agenda today. Are there any other topics people would like to bring up? Okay, in that case before people vanish and well, I saw you close. I heard you Falco, are you there? Falco Yes, I'm here. Excellent. Cool. Did I miss anybody else for the attendance? Doug in here. Oh, I'm sorry. I did notice you there. Sorry, Doug. We forgot about you Thank you All right, anybody else? Okay, in that case this call is over if anybody'd like to stick around for the stk call. We'll start that up um in about a minute or so So we don't have anything to talk about it could be a very short call But if you're interested, please stand the line everybody else. Thank you very much and we'll talk again next week Thank you. Bye Bye We're down to nine people All right, um Everybody ready to just start or do you want to wait another minute? Okay, not hearing any objections. We'll go on and get started. Francisco, you're up first with some Something relative to the java SDK. Do you want to talk about that? Yeah, so basically I've started creating a proof of concept with the java SDK And I found that the dpi's need a little bit of work or rework in my opinion And I and I wish to contribute to it if the maintainer agrees with it uh, so generally, uh I've found that generics are quite painful now Because when you need to write middleware, usually you don't you don't need you don't know and you don't care about the Specification version and the payload that you pass that is inside the event so having to fix those generics is it's quite a problem And also there is this json class which needs a little bit of rework too because there are some methods missing some methods that are quite hard to use so uh, I would love to to hear the comment of who maintains the The gel is decay and I'll be really glad to to work on it together with him. So You did read Fabio's comment here, right? Yeah, I was looking at this It the point is that you don't need generics to be strong-typed I mean like in for example in the rust SDK We are creating a new no time. Uh, we are creating a union type for for being Strongly typed and but at the same time we don't we don't have the pain of knowing in advance What's the cloud events version that you are handling when you read the event? Which is the main problem than now the javas dks so Yeah, I'll try to raise a couple of PRs for this and I just wanted to to know the the comments of Fabio Okay, yeah Yeah, I think he was I think he was hoping to join the call But then I think he got pulled away the last minutes. That's why he left the comments Yeah, but I think he's definitely the main person that you're gonna have to work with on that because he's basically Has been driving the the job SDK for the most part. Okay. Okay. Yeah Also, also he also raised that are good points like removing external dependencies all these things I completely agree with him And there is like for example, there is the iber and validator which is kind of useless Because like for example, when you create middleware Sometimes you just don't need to to body because maybe you don't even know what is inside the event You just want to pass from one point to another so Right and yeah, generally That's that's that's my comments about it. Okay. Um, does anybody else in the call have any comments on this? Otherwise, we'll let those those guys talk about it offline But if you're on the call you want to bring something up go ahead Okay, I guess not Um, next is the rest SDKs or something you want to do that here or just make sure everybody's aware of it Uh No, just I just want to let you know that we are working on this Uh, it's uh, the I think the guys that are working with me, uh, didn't manage to join this call But yeah, that's uh, the the work is starting. We have uh planned the features that we want Now we are working on the data structure and then we will The the plan for the zero point one Is to have the data structure the jason marshaling and marshaling support for zero point three and one point two version And I think those are the most important features that we will have for zero point one Then in the future releases, we will have the mqqtt and and htp because They they they already have the mqtt logic and they and they have the chip logic. So we will merge those two things So did I hear you right that you're gonna support more than just 1.0? Uh Yes, we are going to support zero point three Okay, just out of curiosity Um, does anybody think that they have to support zero point three? So we particularly pick on scott for a second here scott Would it be horrible if they did not support zero point three? I just don't want them to do work that may not be necessary Uh, I don't think that that's uh an unreasonable thing but If you come in and you it's new and And the bar is pretty high to go and back implement all of the wacky features we cut in the spec As long as it's very clear that this thing's only going to work with 1.0 in the documentation Yeah So that's something to keep in mind for just guys you go forward, you know, you don't have to support anything but 1.0 Yeah, I kind of want to drop like 1.1 and 0.2 support and go to be honest. Yeah, those are really painful to support frankly Yeah, I actually know because of all the name changes We had to do a bunch of wacky stuff to make sure it all works. Yeah, also There are also some tests that are flaky because 0.1 and 0.2. So yeah, I I mean, I'm kind of keen on just to lean 1.0 and probably 1.2 You know, it's it's been released for a year now, right? I think it's time to move on So the reason uh to add 0.3 to be honest is that we need somehow uh Two versions of the spec to understand how how to design the the structure Yeah, that's that's a really good point. That's that's that's because because uh designing the structure is not the main problem, but also the The logic to marshal and a marshal That must be based on the spec version So those are the reasons why we want uh way we we decided we agreed on the supporting 0.3 Interesting reason That's a good reason. It's interesting Yeah, I don't think a lot of the specs or a lot of the sdk support the the same level of version compatibility that the the go-ling one does Yeah, I I used to update now. Now that you remember me. I used to all to To do a pr for python sdk to update but I think nobody Think nobody merged it and this pr contains support for 0.3 and a v1 because now sdk python supports only 0.1 and 0.2 Okay, cool. Um All right, so fabio asked about or open up. Um, I'm sorry add us on here about cofka headers um francesco, I think you were Involved in this effect. You actually opened up to guess this issue as pull request. Let's see what you said here So this is a change to the cofka binding So this this basically just mandates that they're all just strings, right? So for now, yes, because uh I mean It could break a lot of things and and it requires a new versioning of the club events specification to have another logic to I mean to have another types right, I think Take this pr more like a not fix Right, and I apologize. I I completely forgot that you opened this pull request Otherwise, I would have brought this up in the main call to draw everybody's attention to it um Anybody having any comments on this it seems reasonable to me But to be honest, I I know next to nothing about cofka. So I I'm not one to say so To be honest, I will I will prefer to have some more efficient encoding But uh It's something a little bit hard and we start touching some chords So it needs to be agreed with several parties because then every every language should should be able to simply implement these encode the encoding logic and so Right For now your tf8 strings are fine Okay Scott claus or anybody else in the call you guys have any thoughts on this I'm gonna assume silence means no I don't know much about cofka. So, okay Okay Um in that case, is there anything else you guys want to talk about? Uh, yeah, I want to add something. Yeah, please go ahead. So And There's so this is something that I brought up in The selection like a couple of weeks ago the whole number Which is about creating a new encoding strategy a new encoding type for the htp binding Uh, so basically now we have this batch this batch which sends events Uh encoded in a json array So it's a json of jons And I will love to explore Uh using multi-part for a multi-part bodies to to send multiple events We actually talked about that at one point and maybe you guys can remember but I could have sworn one of the reasons we pushed back on that was It's it's it's gonna sound like weird, but I think the argument was mainly from clemens saying multi-part mime is hard I think that was the biggest reason I don't know. I don't know whether that's completely true or not, but I think that that's the only thing I can remember Can you can you guys Can you old-timers remember what the reason was that we rejected that? I think it's because of the header issue What? What what you said or can you elaborate? well, I don't I thought the the the issue was that uh multi-part doesn't get unique headers per per body So that's not true because multi multi-part has different versions So uh as different mime types the form data allows only like The file name because it's it's designed for file uploads, but there are different multi-part and there is Basically we can play around this to make uh buy to make a Uh an encoding which works. I mean My question is are you interested on exploring this? So what what I would do is I would open up an issue asking about it because I could just like I said I think we talked about this before and we we didn't have that head down that path for a reason I just can't remember for sure what the reason is, but if you open an issue You'll force someone like clemens to respond to the issue and that will Maybe trigger some people's memory in terms of why we said no in the past And maybe those reasons no longer apply. I I I don't know But if you can open an issue just to force the conversation, I think that'd be good Okay Okay, um, hold on a minute. So this actually it's an sdk issue, but it's a good question. Um I know there just just Before dropping out. I know there a solution we could explore is j-zone streaming Which is nothing more than doing That's sending j-zone new lines separated That's that's that's another thing I I mean, maybe the the right answer here is instead of calling it batch. We call it Event streams for HTTP and one could be multi-part and one can be uh j-zone streams I don't know I have no opinion frankly on the name. I I really don't care I mean what I care is more Deficiency because now batch is extremely inefficient because you you can't send things like in binary. So sending the body It doesn't it removes the the opportunity for doing a lot of Uh optimizations. Yeah, that's There's a bunch of other problems with it. That's why I never implemented it Interesting Well, if you want to force that discussion again, you can again open up another issue on that we can talk about it I would not open up I would not work on a poor request yet until you get some discussion on the issue because I don't want to waste your time But definitely open up an issue to force the discussion Okay, okay Okay, cool. All right. Anything else you guys want to talk about? All right, cool. In that case, we are done Thanks everybody and we'll talk again next week. Actually, I should say for sdk. We'll talk in two weeks um, if for some reason you guys do want to have a call next week just Just ping me to and then we'll I'll I'll announce it to the group that will have a call But usually we don't have enough topics to warrant a call every week. That's why it's every two weeks But we definitely can if you guys have something you want to talk about. Okay, actually, let's let's Plan that for at least the go lang one You want one next week? Yeah, my plan is I'm switching to Cloud events full-time for a couple weeks after this k-native release Okay In that case What is the next one March? What? Do Yeah, I'm going to the symposium It's March 5th. You're gonna be available for it. Uh, let me double check here It's not next week. It's the following week. So yeah, we're good. Okay. And what's the topic again? Uh, we're we're gonna drive to v2 Okay, cool. Okay. I'll try to remember to send that a note to everybody to make sure they know that we will have a call Next week and uh, it's not in two weeks Cool Anything else you guys want to talk about? All right, cool. Thank you everybody. We'll talk again next week Later. Bye