Search by EQ Item ID number? or the link spam string?

[Gaell Stormracer]

Would it be possible to include a search by the EQ item number? and/or the link spam from an item that you get with ;tell <link> ?

(Ideally, should be able to do a "what recipes does this make" search with those -- would save a second query).

[Unapuma]

I think that would be a problem since the EQ ID # doesn't match the ID # of items in EQTrader's database. Maybe one of the web moderator can explain but I'll bet it's not possible.

[KyrosKrane]

I know what you're thinking (based on the other thread), and I'm working on something similar. =) Poke me in a day or two if I don't update this thread.

[Gaell Stormracer]

Thanks KK

[Gaell Stormracer]

/poke KK

My hook script is just waiting for this....

[KyrosKrane]

I haven't forgotten. =) I've got a proof of concept up and running; I'm just waiting for some feedback on whether we actually want to implement this. (There are substantial and valid reasons why we may not want to do this, though I'm not going to discuss them here.)

[Ngreth Thergn]

And I am stubborn about only reading the code back end eqtraders section on weekends so I can concentrate on work doing the week. Kyros is probably waiting on my opinion on something and I will not be giving it until tomorrow

[Gaell Stormracer]

Okay. But this request is only an improvement in efficiency - an exact lookup vs a fuzzy text search followed by a "recipes using this" search -- the LATTER already works.

(EDIT: former vs latter...)

[Gaell Stormracer]

Any more feedback on this?

[KyrosKrane]

Coding's done, just waiting for the official announcement. =)

[Aelfin]

I see the announcement. Any chance at an XML web service? Come on, think RESUME BUILDING!

[Gaell Stormracer]

What's "RESUME BUILDING"?

I don't know if a pure "database server" would be a good idea, because there'd be no possibility of the Google ads helping to offset the extra workload, and because that might make it too easy for a data mining app to hammer the service...

[KyrosKrane]

Yeah, I doubt this would happen for a couple of reasons. First, like Gaell said, there's the issue of cost, and second, I'm not sure the database server could take the extra load.

Technically, it's pretty easy to code an XML quasi-service. (I wouldn't do it as a full-blown Web service, just a simple ID in the query string to return a pageful of XML.) But that opens the door to too many problematic issues.