Andreas Junghans <[EMAIL PROTECTED]> writes:
> It's not about any significant advantage. It's just what the JavaScript
> language specification allows when calling Date.UTC. Of course, there's no
> need for us to follow this (after all, _we_ are the ones deciding which
> subset of JavaScript we
Hi Derrell,
Am 22.06.2006 um 15:41 schrieb [EMAIL PROTECTED]:
> Andreas Junghans <[EMAIL PROTECTED]> writes:
>
>> I'll adapt the Java implementation to handle numbers that are
>> left out
>> (currently, only the milliseconds are treated as optional).
>> Looking at the
>> JavaScript referenc
Andreas Junghans <[EMAIL PROTECTED]> writes:
> I'll adapt the Java implementation to handle numbers that are left out
> (currently, only the milliseconds are treated as optional). Looking at the
> JavaScript reference, only year and month are mandatory. Should we handle it
> the same way (i.e.
"Danny Adair" <[EMAIL PROTECTED]> writes:
> But why handle it differently on the server side?
> Why a _data_ field, why not just a (service,) method, params and id field?
When a message is being sent, the choice of which transport to use is done way
down in the bowels of the RemoteRequest process
Sebastian Werner <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] schrieb:
>> I've just checked in the first draft of a new JSON-RPC Server Writer's
>> Guide. It's in the 'namespaces' branch, in the 'backend' directory. I'd
>> certainly appreciate comments and suggests for improvement!
>
> Mhh, w
Hi Danny and Derrell,
Am 22.06.2006 um 04:54 schrieb [EMAIL PROTECTED]:
> "Danny Adair" <[EMAIL PROTECTED]> writes:
>
>> 1. What about simple dates of the form "new Date(Date.UTC
>> (2006,6,20))". It
>> seems cumbersome to specify zeros all the way down to the
>> milliseconds when
>> you don't
see belowOn 6/22/06, [EMAIL PROTECTED]
<
[EMAIL PROTECTED]> wrote:"Danny Adair" <
[EMAIL PROTECTED]> writes:> Thanks Derrell,>> Looks good. I might have some more questions once I start implementing.>> For now,>> 1. What about simple dates of the form "new Date(
Date.UTC(2006,6,20))". It> seems c
[EMAIL PROTECTED] schrieb:
> I've just checked in the first draft of a new JSON-RPC Server Writer's Guide.
> It's in the 'namespaces' branch, in the 'backend' directory. I'd certainly
> appreciate comments and suggests for improvement!
Mhh, what's about to put this in the wiki instead of the SVN
"Danny Adair" <[EMAIL PROTECTED]> writes:
> Thanks Derrell,
>
> Looks good. I might have some more questions once I start implementing.
>
> For now,
>
> 1. What about simple dates of the form "new Date(Date.UTC(2006,6,20))". It
> seems cumbersome to specify zeros all the way down to the millisecon
Thanks Derrell,Looks good. I might have some more questions once I start implementing.For now,1. What about simple dates of the form "new Date(Date.UTC(2006,6,20))". It seems cumbersome to specify zeros all the way down to the milliseconds when you don't care about time. As usual, 0 would be assume
I've just checked in the first draft of a new JSON-RPC Server Writer's Guide.
It's in the 'namespaces' branch, in the 'backend' directory. I'd certainly
appreciate comments and suggests for improvement!
Cheers,
Derrell
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Full
11 matches
Mail list logo
