Skip to content
This repository was archived by the owner on Sep 3, 2024. It is now read-only.

Setting "Request Type" does not seem to take effect #18

Closed
ghost opened this issue Mar 16, 2015 · 4 comments
Closed

Setting "Request Type" does not seem to take effect #18

ghost opened this issue Mar 16, 2015 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Mar 16, 2015

I have set Request Type to something other than AUTODETECT, but it still attempts to autodetect. Is this field being used when connecting?

@2m
Copy link
Contributor

2m commented Mar 16, 2015

After a quick look at the code it seems that it is not used when calling iodine native code.

@ghost
Copy link
Author

ghost commented Mar 16, 2015

Not sure if I'm going crazy, but I think it tried to use a specific record type that I selected, but it wasn't the one I had set at the time.

I also see what you mean about it not being called, so perhaps I am indeed just going crazy.

@2m
Copy link
Contributor

2m commented Mar 16, 2015

Looking more at the code it seems that it is always autodetecting request type irregardless of the selected request type.

@yvesf
Copy link
Owner

yvesf commented Mar 17, 2015

I can confirm that. Looks like I forgot about that aspect after modeling the Configuration.
Basically it's just a matter of converting the Java-Enum to string and adding to Java_org_xapek_andiodine_IodineClient_connect and calling client_set_qtype("A") with it.

@yvesf yvesf added the bug label Jun 14, 2015
yvesf added a commit that referenced this issue Nov 29, 2016
@yvesf yvesf closed this as completed in 52914b0 Dec 1, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants