Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dart VM needs hot swap functionality when executing server-side #15318

Closed
DartBot opened this issue Nov 26, 2013 · 5 comments
Closed

Dart VM needs hot swap functionality when executing server-side #15318

DartBot opened this issue Nov 26, 2013 · 5 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. type-enhancement A request for a change that isn't a bug

Comments

@DartBot
Copy link

DartBot commented Nov 26, 2013

This issue was originally filed by danil.kornishev@gmail.com

To enable rapid development, it should be possible for changed code to be swapped into running VM.
JVM and PHP have this ability.

Current development flow for server-side components is quite awkward with server needing to be restarted for every change.

This functionality could be accomplished by a complete re-load of VM (easier) or only swapping relevant libraries.

Expected Flow:
Change file -> Save -> Relevant code in memory is refreshed
@iposva-google
Copy link
Contributor

Added this to the Later milestone.
Removed Type-Defect label.
Added Type-Enhancement, Area-VM labels.

@iposva-google
Copy link
Contributor

Added Triaged label.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@DartBot DartBot added Type-Enhancement area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Aug 4, 2014
@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed priority-unassigned labels Feb 29, 2016
@rmacnak-google
Copy link
Contributor

Hot reload is available via the VM-service and Observatory. It is suitable for use at a development time, but it lacks user-defined schema migrations one would expect for hot swapping code in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kevmoo @kasperl @iposva-google @rmacnak-google @DartBot