Hi Thomas,
these are great ideas and could be implemented in my - admittedly hacky -
approach! I agree that the request should be part of the data and that one
file should contain more than one request. I don't think I'll be able to do
this this week, but it will be coming! Probably we need a "Record", "Pause",
"Discard" and "Save" Button for the recording of the requests, then.
As to a more comprehensive solution - I fully agree with you that something
more stable is needed. My solution was simply to be a quick-and-dirty way to
create interactive demos without a server backend. So I think that both
appraoches target different use cases.
So let's keep thinking and developing this further!
Christian
I see the need
thron7-2 wrote:
>
>
>> MRpcMockup:
>> - comfortable
>> - tight coupling
>> - relies on Rpc internals (unreliable interface)
>> - only for ad-hoc, interactive usage
>>
>>
> So, saving rpc traffic data to file is there, but I see you only capture
> the response data. I'm not sure this is sufficient. You pick up
> responses in the mockup mode by going through the hash of the rpc
> signature (prob. over something like service-name/params), right?! But
> the request signature is only captured as comments. I think it would be
> better a part of the generated Json. Capture data should be
> self-contained, to the extend that a single Json key (the request hash,
> if you will) contains subkeys "request" and "response" that represent
> both sides of the request in a standardized why. I think this would be
> way more useful.
>
> The Json file format should also allow for more than one request per
> file. This is probably nothing you could support on the capturing side,
> but would be done by hand. But the replay facility should be able to
> handle this, so you can pass, say, 1,000 requests within a single file.
> Something like this:
>
> {
>
> "deb693849aab654cde5261a77ae8c0f41943dc60":
> {
> "request" :
> {
> "serverUrl" : "http://.../RpcPhp/1.0.1/services/index.php";,
> "serviceName" : "qooxdoo.test",
> "serviceMethod" : "echo",
> "params" : ["Hello World"],
> "serverData" : null
> },
> "response" :
> {
> "id" : 4711,
> "error" : null,
> "response" : "Client said: [Hello World]"
> }
> },
>
> "x5z693849aab654cde5261a77ae8c0f41943dc60":
> {
> "request" : ...,
>
> "response" : ...
> },
>
> ...
> }
>
> T.
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
--
View this message in context:
http://n2.nabble.com/New-contrib-releases-RpcConsole-RpcPhp-RpcPython-tp4084412p4087710.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
