veyepar: Getting into the Rusty Bucket: Lessons from Integrating Rust with Existing C

Author(s):	William Brown
Location	Tasman Hall B/C
Date	jan Thu 19	Days Raw Files
Start	20:20	First Raw Start	19:59
Duration	0:45:0	Offset	0:20:12
End	21:05	Last Raw End	21:29
Chapters	00:00 0:09:36 0:38:47 0:39:35
Total cuts_time	44 min.

http://linux.conf.au/schedule/presentation/51/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Getting_into_the_Rusty_Bucket_Lessons_from_Integrating_Rust_with_Existing_C.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Rust is a modern language developed by Mozilla pursuing the trifecta: Safety, Speed, and Concurrency. With such promise for the future, how can we use this now? We are not always in the beautiful open green fields; we must contend with our existing grunty applications! 389 Directory Server is based on code now more than 20 years old. We cannot throw this out and replace it, but we want the benefits Rust gives us - especially for authentication and security critical code. We will explore the challenges of security in engineering, and behaviours of the modern programmer. I will discuss why we have spiraled down a mountain of failure as an engineering discipline - and why we need tools like Rust to validate our work. I will explore the Directory Server plugin interface, where we have the ability to provide pure Rust plugins, allowing safe, fast extensibility to a core piece of systems authentication. This will explore the challenges to build it, and the design patterns needed in C, to make sure that the integration between Rust and C is possible today, leading towards a future rewrite. markdown
Comment:	production notes

2017-01-20/13_59_48.ts Apply: 21:04:55 - 21:15:49 ( 00:10:54 ) S: 20:59:48 - E: 21:29:48 D: 00:30:00 (Start: 307.0) (End: 961.0) show more...

vlc ~/Videos/veyepar/lca/lca2017/dv/tasman_bc/2017-01-20/13_59_48.ts :start-time=0307.0 --audio-desync=0

	Raw File	Cut List
	20:59:48		seconds: 307.0 Wall: 21:04:55
Duration	00:30:00
	21:29:48		seconds: 961.0 Wall: 21:15:49
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this

Rf filename:

root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv

Sequence:

get this:

check and save to add this