rion> Jingle-FT::File: OPTIONAL, but SHOULD be present when offering a file.
Can we change SHOULD to MUST here?
rionit's for "size" attribute
rions/attribute/element/
rionsending files being changed is not a good idea anyway
waqasFile systems exist where file size isn't known in advance
rionin use nowadays?
remkohas joined
waqasCertainly, e.g., /proc on Linux
Alexhas left
Kevhas left
rionwell ok I guess there are people who ever send files from /proc. certainly not me though.
waqasA generic file transfer building block is useful, e.g., I may choose to offer webdav like services. Note that size tends to be optional in almost all file transfer oriented protocols. Almost nothing mandates it.
rionin any case if I ever sinde files from proc I'd made a cache first
goffihas left
goffihas joined
waqasYou are thinking of "rion's specific use-case", and not of "general protocol building block usable in a variety of situations"
waqasI sympathize FWIW :)
rionok ok =)
waqasAnd you can always cache on the receiver side :)
waqasSame is true for HTTP/webdav/etc, FTP, SFTP, email protocols, etc
waqashas left
alacerhas joined
adityaborikarhas joined
Mikaelahas joined
rtq3has joined
mimi89999has left
mimi89999has joined
Steve Killehas left
sezuanhas joined
remkohas left
remkohas joined
lnjhas joined
sezuanhas left
sezuanhas joined
jcbrandhas joined
alacerhas left
alacerhas joined
Steve Killehas joined
Kevhas joined
Lancehas left
Andrew Nenakhovhas left
Andrew Nenakhovhas joined
Andrew Nenakhovhas left
Lancehas joined
Andrew Nenakhovhas joined
alacerhas left
alacerhas joined
neshtaxmpphas left
igoosehas left
lskdjfhas joined
igoosehas joined
larmahas left
Lancehas left
larmahas joined
Danielhas left
Danielhas joined
Danielhas left
Danielhas joined
alacerhas left
mimi89999has left
adityaborikarhas left
mimi89999has joined
adityaborikarhas joined
lskdjfhas left
rtq3has left
Lancehas joined
zachhas left
zachhas joined
alacerhas joined
Steve Killehas left
Danielhas left
Danielhas joined
rtq3has joined
Danielhas left
Danielhas joined
Danielhas left
Danielhas joined
Danielhas left
Danielhas joined
Danielhas left
Danielhas joined
Danielhas left
Danielhas joined
Danielhas left
Danielhas joined
neshtaxmpphas joined
flowrion, what would be the benefit of s/SHOULD/MUST/ here?
COM8has joined
COM8has left
COM8has joined
COM8has left
debaclehas joined
Danielhas left
Danielhas joined
curenhas joined
Danielhas left
Danielhas joined
eevvoorhas joined
adityaborikarhas left
adityaborikarhas joined
Kevhas left
Lancehas left
alacerhas left
alacerhas joined
lskdjfhas joined
alacerhas left
adityaborikarhas left
adityaborikarhas joined
Mikaelahas left
frainzhas left
frainzhas joined
Mikaelahas joined
alacerhas joined
Nekithas left
Nekithas joined
alacerhas left
pdurbinhas left
alacerhas joined
karoshihas left
karoshihas joined
eevvoorhas left
alacerhas left
neshtaxmpphas left
Kevhas joined
igoosehas left
igoosehas joined
Alexhas joined
Nekithas left
Nekithas joined
goffihas left
murabitohas left
murabitohas joined
igoosehas left
lumihas joined
igoosehas joined
goffihas joined
sonnyhas joined
alacerhas joined
matlaghas left
matlaghas joined
pdurbinhas joined
alacerhas left
alacerhas joined
igoosehas left
alacerhas left
alacerhas joined
alameyohas left
alameyohas joined
pdurbinhas left
rionKnowing full size in advance it's somewhat easier to operate with ranged transfers
rtq3has left
alacerhas left
Zashhas joined
moparisthebestrion: what if I'm sending you a flac as an mp3 and just converting it on the fly or something
Lancehas joined
patrickhas joined
Zashhas left
Zashhas joined
devhas joined
devhas left
devhas joined
devhas left
devhas joined
devhas left
devhas joined
devhas left
devhas joined
devhas left
alacerhas joined
devhas joined
devhas left
devhas joined
devhas left
flowrion, sure it is, but what has this to do with s/SHOULD/MUST/?
flowi guess my point is that most implementation will send the size if they know it, while there may be cases where you do not know the size in advance
eevvoorhas joined
flowand if we s/SHOULD/MUST/ then those cases would no longer be compliant
devhas joined
devhas left
flowwhich probably would not prevent those implementations to perform file transfers without size announcing the size
COM8has joined
Lancehas left
COM8has left
igoosehas joined
rtq3has joined
eevvoorhas left
eevvoorhas joined
Lancehas joined
Ge0rGhas left
Ge0rGhas joined
Andrew Nenakhovhas left
pdurbinhas joined
rtq3has left
kokonoehas left
kokonoehas joined
rtq3has joined
eevvoorhas left
Lancehas left
rionI agree with you guys :)
I just thought I can really use it to stream endless media.
I already see this SIMS with an online translation :)
rionover s5b =)
pdurbinhas left
eevvoorhas joined
adityaborikarhas left
adityaborikarhas joined
Lancehas joined
murabitohas left
murabitohas joined
Lancehas left
eevvoorhas left
stpeterhas joined
peterhas joined
Lancehas joined
debaclehas left
mimi89999has left
mimi89999has joined
sezuanhas left
wojtekhas joined
curenhas left
pdurbinhas joined
lovetoxhas joined
pdurbinhas left
mimi89999has left
mimi89999has joined
ZashWhat would be a good way to represent a datetime delta in a dataform?
neshtaxmpphas joined
jonas’seconds as floating point?
ZashFor eg MAM retention periods and such
jonas’it’ll be a PITA
ZashXEP-0122 has datetime but that's not quite right