[geeklog-devel] gsoc notification system
wojtek.szkutnik at gmail.com
Sun Mar 21 16:02:13 EDT 2010
Whoa, guys, SOAP, RPC, JSON? Really? Correct my if I'm wrong, wasn't the
goal of this task creating something inside the system? The JSON stuff is
great for communication between web apps etc but what's the point of using
it on the inside? I was thinking about implementing something more
listener-like, close to the scheme from the document. A set of
listeners/observers/"event throwers" would do the trick very well, without
any unnecessary sophistication. * **Simple is better than complex**. Complex
is better than complicated.** *, right? ;-)
On Sun, Mar 21, 2010 at 7:26 PM, ganesh <th3iedkid at gmail.com> wrote:
> Hi Mr.Dirk and to all the developers ,
> Hello there!
> Well you were right in assuming about the SOAP getting used directly,
> because i have been trying to develop a lightweight JSON-RPC scheme under
> php for some time now for my pet-project.Currently i use a C++ based json
> scheme to respond due to my efficiency considerations, i however combined it
> with php with leveled caching scheme i developed for it to handle heavy
> requests. I chose* json because of its ajaxian benefits* i derive by
> delegating the user requests into different levels i classified them into so
> that these requests could be cached out based on the level they belong to.
> However could you help me point the possible damage json-rpc based schemes
> could do, and the damages of json could also be specifically pointed out if
> possible for them getting used in the notification system structurally.
> I havent been able read all the discussions on last year's notification
> system idea for gsoc due to the local connectivity problems i faced for some
> time, now tht its back n running i will go through them,thanks a lot for
> the link , it gave an excellent start for the skeletal design i wish to make
> for the notification system
> Thanks and regards
> On Sat, Mar 20, 2010 at 2:01 AM, Dirk Haun <dirk at haun-online.de> wrote:
>> ganesh wrote:
>> >As for the notification service under the core ,i was thinking in the
>> >of SOAP model for a web-service which could provide a scheme for event
>> >reception,confirmation and notification.If i were to develop a core API
>> >under these lines , the services provided could then be used by the
>> >and other actors with the under-core implementation staying opaque.Please
>> >check me in my line of thought if am going in the right direction.
>> Yes, I think that's a good general subscription of the idea. Actually,
>> you mentioning SOAP scared me a bit ;-) But I think you really only
>> meant that, effectively, this would be along the lines of what SOAP
>> tries to accomplish and you are not suggesting to actually use SOAP
>> here, right? Just checking ...
>> If you haven't done so, you should also read through the past discussion
>> (linked from the wiki page). I see that Konstantin's draft is still
>> You may be able to draw some inspiration from that as well.
>> bye, Dirk
>> geeklog-devel mailing list
>> geeklog-devel at lists.geeklog.net
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geeklog-devel