That's exactly what people usually say before they go into finding out WHY. Don't touch it damnit!!

Got some errors also tho, but otherwise it's working ok now.:

2012-11-13 22:13:24,696 INFO proxy getwork_listener._on_submit # [178ms] Share from 'kimitobo_Fury' accepted, diff 3
2012-11-13 22:13:25,873 INFO proxy jobs.submit # Submitting 09b88f5d
2012-11-13 22:13:26,051 INFO proxy getwork_listener._on_submit # [177ms] Share from 'kimitobo_Fury' accepted, diff 3
2012-11-13 22:13:27,471 INFO proxy jobs.submit # Submitting 5767cbd9
2012-11-13 22:13:28,445 INFO proxy getwork_listener._on_submit_failure # [972ms] Share from 'kimitobo_Fury' REJECTED: (20, u"'data'", u'Traceback (most recent call last):\n  File "./eloipool.py", line 525, in receiveShare\n    checkShare(share)\n  File "./eloipool.py", line 386, in checkShare\n    MWL = workLog[None]\nKeyError: None\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File "/opt/eloipool/stratumserver.py", line 76, in found_terminator\n    rv = getattr(self, funcname)(*rpc[\'params\'])\n  File "/opt/eloipool/stratumserver.py", line 159, in _stratum_mining_submit\n    self.server.receiveShare(share)\n  File "./eloipool.py", line 533, in receiveShare\n    share[\'solution\'] = b2a_hex(swap32(share[\'data\'])).decode(\'utf8\')\nKeyError: \'data\'\n')

No, stratum isn't http. stratum+tcp://us2.eclipsemc.com

cgminer's stratum implementation is broken. I've got some fixes in BFGMiner git, but I hear Con's making excuses.

According to the wikki on Ver 2.0

id: An identifier established by the Client that MUST contain a String, Number, or NULL value if included. If it is not included it is assumed to be a notification. The value SHOULD normally not be Null [1] and Numbers SHOULD NOT contain fractional parts [2]

It seems like luke-jr misunderstands what a client is. The client is CGminer. Also in no example I have found in the documentation was id anything but an integer. This doesn't mean it has to be but if every example has it being so then it seems like a precedent. It seems like id is used instead of method. Shouldn't it be like this?
{"jsonrpc": "2.0", "method": "auth", "id": (whatever the client sent)}

According to the Stratum Documentation.

Response
    Every response contains following parts
◦message ID - same ID as in request, for pairing request-response together
◦result - any json-encoded result object (number, string, list, array, …)
◦error - null or list (error code, error message)

While true it says that any string, number or NULL value is required, it also stated it is selected by the client. I am not 100% positive on the rest I didn't write the specs or anything. I just read them. I really don't see why a person wouldn't want authorized before they get a difficulty.

As I see it and maybe I am totally wrong but I want to try stratum on EMC. Since authorize can come at any time why can't it come before subscribing?

So, how to I use stratum on EMC?

help?

Derp!

It was my understanding subscribe can come at anytime, but authorize has to come are a more specific time (beginning of the session), is that wrong?

I don't see any sense in limiting variable difficulty to integers.  I'm interested in hearing your idea.

My argument to that would be: Why would such fine-grained difficulty be required?

Sometimes 'good enough' is acceptable

I'll try your patch when I get time, maybe tonight.

I'm open to a change in EMCs way of doing it, but it seems like it's working fine in all the miners right now and it's just a JSON issue at the moment that can be fixed fairly easily one way or another. 

so its a HACK where mined shares will get lost... (in some cases)
[/quote]

Hack, yes, but no shares will be lost. The miner will just send shares which are under the pools target difficulty, so will be rejected.
That is, they'll be rejected by the pool, rather then internally in the miner software.