Unhandled error event about node-dhcp HOT 7 CLOSED

What do you mean by handling it with the options file? Throwing an exception is meant to push the admin more rigoros on the issue, which might be an inacceptable behavior in some cases. Do you want to have a default case instead of throwing?

from node-dhcp.

Yes, I think that's what I was trying to convey, a default case would be perfect. :>

from node-dhcp.

Hmm, I think it's hard to define a default case since all unimplemented options have different types. What I can think of instead of throwing an error I could just invoke the error handler, so you can catch these cases with on("error")

from node-dhcp.

that would be perfect, logging the info works perfectly fine too. It's impossible to cover every use-case but we also don't want the system to die out when it can't handle something. Never know what kind of junk devices request these days!

from node-dhcp.

Yeah, you're absolutely right! I did it the hard way to see problems immediately while developing. But I will change it :)

from node-dhcp.

^--- best customer service right here.

from node-dhcp.

Thanks :) v0.2.18 just landed on npm.

from node-dhcp.